tags 399751 + fixed-upstream
thanks

Hello!

On Mon, 15 Oct 2007 01:41:10 +0200, Alberto Bertogli wrote:
> On Sun, Oct 14, 2007 at 10:48:28PM +0200, Luca Capello wrote:
>> The main reason against the change is if /etc/darcsweb/ is intended
>> to store other than a single file, config.py, which doesn't seem
>> the case ATM.
>
> I'm sorry, but I honestly don't believe this is worth breaking
> backwards compatibility. If it's just to avoid creating a directory
> that in the future might even be necessary or desirable, I don't
> think it's worth it.

Your point, anyway you're the upstream ;-)

>> I don't know anything about python, but what if the first place in
>> sys.path contains a config.py?  The problem should be the same :-(
>
> The first place is always '.', that's why it works: it looks in the
> same directory as darcsweb for a config file, and if it can't find
> one, it looks in /etc/darcsweb.

Thank you for the explanation.

> That way you can have multiple darcswebs on the same machine with
> different configurations, and avoid the name clashing with other
> python modules.

And after considering your point, this is fine as well.

I just discovered that you fixed this upstream with patch:
=====
Sun Oct 14 17:42:34 CEST 2007  Alberto Bertogli <[EMAIL PROTECTED]>
  * Add /etc/darcsweb after '.' in sys.path.

  Add it second place, so it goes after '.' but before the normal path. This
  allows per-directory config files (desirable for multiple darcsweb
  installations on the same machin), and avoids name clashing if there's a
  config.py in the standard path.

  This was reported by Philipp Kern <[EMAIL PROTECTED]> in Debian bug 399751
  (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399751).
=====

Thus, I accordingly tagged the bug.

Thx, bye,
Gismo / Luca



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to