> On 4 May 2016, at 14:09, Sandro Tosi <[email protected]> wrote: > > On Wed, May 4, 2016 at 1:54 PM, James Clarke <[email protected]> wrote: >> Hi, >>> On 4 May 2016, at 13:41, Sandro Tosi <[email protected]> wrote: >>> >>> Package: pbuilder >>> Version: 0.223 >>> Severity: normal >>> >>> Hello, >>> currently network access is disabled by default (which is great!) but if you >>> want to enable it (there are good cases), the only way i can see is thru the >>> config file. >>> >>> I would be useful to have a cli switch to enable/disable network access, so >>> that >>> it could be an option of that single build, and not enabled for all the >>> builds. >> >> You can always use --configfile to point to a file with USENETWORK=yes > > so i would need to copy the current configfile, add a line and use it? > that seems a good way to have the 2 files misaligned
No, just the single line.
>> (which could be using the <(echo "USENETWORK=yes") bashism if you want a
>> true one-liner).
>
> which means i lose all the configurations in the configfile
From pbuilder(8) man page:
--configfile [configuration file to load]
Additional configuration file to read after all other configura‐
tion files have been read.
It’s cumulative; nothing gets lost apart from those variables you override.
>> We could still have a --use(-)network flag for convenience though, so
>> leaving this open.
>
> yeah that's exactly what i need, a cli switch that just enable the
> network access for this specific execution of pbuilder leaving all the
> other configs are they are.
Sure, a single option would be more convenient, but you can achieve it now in a
one-liner. Adding a command-line option for every variable you can have in a
config file would make the command-line very crowded though...
Regards,
James
signature.asc
Description: Message signed with OpenPGP using GPGMail
