On 11 September 2019 20:24:07 BST, gregor herrmann wrote:
>On Wed, 11 Sep 2019 16:22:18 +0100, Ian Jackson wrote:
>
>> One example is:
>>export-dir (gbp)
>>buildresult (pbuilder)
>>build-products-dir (dgit)
>>build-dir (sbuild)
>>
>> So, it would be good for there to be a single w
On Thu, Sep 12, 2019 at 3:24 AM gregor herrmann wrote:
> ~/.devscripts already exists (typically) which similar variables,
> maybe this could be re-used?
Using ~/.devscripts means running shell and passing variables out of
it, which is quite hard to get right. The devscripts config loading
module
On Wed, 11 Sep 2019 16:22:18 +0100, Ian Jackson wrote:
> One example is:
>export-dir (gbp)
>buildresult (pbuilder)
>build-products-dir (dgit)
>build-dir (sbuild)
>
> So, it would be good for there to be a single way to configure these
> things. Every tool ought to look in this si
Quoting Russ Allbery (2019-09-11 18:15:45)
> I think this is a good idea.
+1
Patches to sbuild welcome!
I wonder which configuration should take precedence in case a setting is
specified in the common configuration file as well as in another way that the
program understands -- probably the latte
I think this is a good idea.
Ian Jackson writes:
> It shouldn't just be an environment variable because that clutters the
> environment unnecessarily. I think it should probably be a config
> file in ~, overrideable with an environment variable. (Or perhaps the
> config filename could be overr
5 matches
Mail list logo
