> > > I kinda like the idea of prefixing *all* temporary directory with
> > > a '_'
> > Completely reasonable and almost auto-explaining, I'd say. +1 for
> > Michael's suggestion.
>
> What about placing temporaries below debian/build/? Anything where
> names
> aren't fixed in Policy, i.e. which
Hi,
> > If you want to avoid name collisions, you could also use
> > debian/_build
> > I kinda like the idea of prefixing *all* temporary directory with a '_'
> Completely reasonable and almost auto-explaining, I'd say. +1 for
> Michael's suggestion.
What about placing temporaries below
Michael Biebl dijo [Mon, May 04, 2020 at 11:51:05AM +0200]:
> >> Personally, I don't see any real benefit of standardizing on (making up an
> >> example here) debian/.build over debian/build.
> >
> > Same here. The arguments against debian/build are very weak. If we care
> > about a source
Am 04.05.20 um 09:55 schrieb Raphael Hertzog:
> On Sat, 02 May 2020, Scott Kitterman wrote:
>> Personally, I don't see any real benefit of standardizing on (making up an
>> example here) debian/.build over debian/build.
>
> Same here. The arguments against debian/build are very weak. If we care
On Sat, 02 May 2020, Scott Kitterman wrote:
> Personally, I don't see any real benefit of standardizing on (making up an
> example here) debian/.build over debian/build.
Same here. The arguments against debian/build are very weak. If we care
about a source package building a binary package named
On 5/3/20 5:54 PM, Holger Levsen wrote:
> On Sun, May 03, 2020 at 10:56:32PM +0200, Simon Richter wrote:
>> Frankly, I don't see the point in hiding the directory. The only person
>> who'd ever look into that directory would be someone inspecting what
>> happened during a build process, and all
On Sun, May 03, 2020 at 10:56:32PM +0200, Simon Richter wrote:
> Frankly, I don't see the point in hiding the directory. The only person
> who'd ever look into that directory would be someone inspecting what
> happened during a build process, and all that hiding directories
> achieves is adding
Hi,
On 02.05.20 17:53, Andreas Metzler wrote:
> I do think it is a splendid idea to separate generated stuff from
> everything else, I think there is no real good reason for using a
> hidden toplevel directory.
Frankly, I don't see the point in hiding the directory. The only person
who'd ever
On Saturday, May 2, 2020 11:53:26 AM EDT Andreas Metzler wrote:
> In gmane.linux.debian.devel.general Niels Thykier wrote:
> [...]
>
> > 3) We followed up with an [update to the proposal] were debhelper would
> >
> > optionally expose some of the relevant directories (some by default,
> >
In gmane.linux.debian.devel.general Niels Thykier wrote:
[...]
> 3) We followed up with an [update to the proposal] were debhelper would
> optionally expose some of the relevant directories (some by default,
> others on request) with symlinks while still supporting the new
> layout.
Guillem Jover:
> Hi!
>
> We currently have many built artifacts being dropped directly under
> debian/ or under tool specific directories such as debian/.debhelper/.
> These have at least the following problems:
>
> - Make cleaning, an operation that requires executing code from the
>
11 matches
Mail list logo
