Hi,
> > That's a personal preference, and an unusual one.
>
> Perhaps it's a personal preference, however other programs permit
> overriding the default configuration in some way, rarely is this used
> as an extension point
The contents of --configfile does override the contents of
~/.pbuilderrc.
> Here's why I came to reporting this bug: I have a complex setup which
> does a lot of things "automagically", such as creating distribution
> specific dirs. My default distribution is sid, so I had a .pbuilderrc
> which set distribution to sid, and other *.pbuilderrc for other dists.
> Building for -- say -- etch would happen with pbuilder --configfile
> etch.pbuilderrc. But I noticed that the sid dirs were created
> unconditionally because ~/.pbuilderrc was always sourced.
>
> Now I don't use ~/.pbuilderrc anymore, I have a sid.pbuiderrc as well,
> this makes ~/.pbuilderrc useless to me and it broke my expectation.
> Another way to close the bug is to document this more proeminently in
> pbuilder(8) as it currently states "Loads the configuration file" in
> --configfile. This doesn't contradict what --configfile really does,
> but still...
This sounds like what you really need documentation, do you have a
suggested fix?
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
