[build2] possible to do something similar to DESTDIR= make install?

[Norbert Lange]

Hi

> As I mentioned in one or my previous emails, using the build2-toolchain
> archive (which includes, bpkg, other libraries, etc.) is probably the
> wrong approach when packaging for a distribution. Instead, I would
> suggest that you get build2 and libbutl as individual archives and
> then follow instructions in build2/INSTALL:
>
> https://cppget.org/build2
> https://cppget.org/libbutl

Sure, I just did a quick job to be able to try out build2.
I am not yet sure what to think of it, as you undoubtedly know docs
are sparse =)

> Also, it is not clear to me why you need to clean things. Maybe if you
> can explain the motivation I can suggest a solution (like building
> things out-of-tree).

I always prefer building out-of-tree, but this might be just a personal thing.
For debian, the common package management scripts will do a clean
build for reliability,
its not strictly necessary but its very annoying if this functionality
is missing,

eg. someone wants to build this package -> it fails
someone fixes the issue -> it won`t build again because of
left-over-stuff does not get cleaned
someone can now extract his changes, delete everything, unpack again
and add back his changes -> repeat step 1

Especially nasty if you are new to this =(

Apart from being helpful for users, its required by debian policy:
https://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules

>> > Those are actually generated[1] (and we distribute pre-generated copies
>> > for convenience). So this should be harmless.
>>
>> In the context of above, its not. those files are necessary for the
>> bootstrap I think.
>
> Yes, good point.
>
>
>> Ideally I would be able to build the bootstrap-phases in a separate
>> directory, that`s easy enough to clean up.
>
> Ok, let me see what I can come up with. Will need to brush up on my
> make-fu ;-).
>
> Boris

You know, I can just copy the directories meanwhile, so its not urgent.

Norbert