Hi,
Okay, that's a different behavior for cowbuilder vs pbuilder. I'm not
sure what would ultimately be a desirable way to do it.
At Wed, 28 Apr 2010 08:45:14 +0200,
Yves-Alexis Perez wrote:
>
> severity 579506 minor
> retitle 579506 --configfile option doesn't pick non standard options from
> original config files
> thanks
> On mer., 2010-04-28 at 08:36 +0200, Yves-Alexis Perez wrote:
> > Package: cowbuilder
> > Version: 0.61
> > Severity: normal
> >
> > Hi,
> >
> > cowbuilder manpage says that:
> >
> > --configfile [configuration file to load]
> > Additional configuration file to read after all
> > other configuration files have been read.
> >
> > so I take that as the config file passed in argument will only override
> > settings previously defined, and I just need to set the ones I need.
> > However, it seems that it doesn't work, if I do that, options set in
> > .pbuilderrc are not used, only the one from --configfile are taken.
>
> Hmhm, sorry, I take that back. Only the non-standard options defined
> in .pbuilderrc are not taken in the file passed by --configfile.
>
> For example I define in .pbuilderrc
>
> arch="amd64"
> DISTRIBUTION=sid
> BASEDIR=$HOME/debian/pbuilder
> BASEPATH=$BASEDIR/base-${DISTRIBUTION}-${arch}.cow
>
> and in .pbuilderrc-experimental-amd64 I do:
>
> DISTRIBUTION=experimental
> BASEPATH=$BASEDIR/base-${DISTRIBUTION}-${arch}.cow
>
> then dumpconfig shows:
> basepath: /base-experimental-amd64.cow
>
> while if I redefine BASEDIR=$HOME/debian/pbuilder
> in .pbuilderrc-experimental-amd64 it does work fine.
>
> I guess it makes sense, but it'd be nice if all the variables where
> taken from the original config file. I know the manpage says unknown
> options are ignored, but the current behavior (which ignores them but
> treat them correctly when they are used to defined known options) is
> really helpful.
>
> Thanks for your attention :)
> --
> Yves-Alexis
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
