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

[Norbert Lange]

I managed to get a usable package. I implemented a manual cleanup, so
I don`t depend on a built bootstrap binary and fail otherwise.
For ease of use, I added the build2/libutil sources:
https://github.com/nolange/deb-build2-toolchain/releases/tag/0.7.0-1

I had to limit the directories build will search, since the necessary
debian subdirectory is enough to make it stop.
on that note, I am bit concerned that accidentally typing in the wrong
terminal b could traverse huge directory trees and "update" files it
should not?
(just for kicks: it will segfault when done in / for me)

some quirks are still with the library, do you intent to version by
some custom filename scheme?
(package names of shared libraries should be identical to their soname/filename)


2017-08-21 23:06 GMT+02:00 Norbert Lange <nolange79 at gmail.com>:
>>> I will have to build "in-tree", and take some care to be able to clean
>>> up everything.
>>
>> I've fixed the version cleanup and restaged the new version (available
>> from the same place) so the in-tree build should now be compatible with
>> the "Debian way" without any extra effort.
>
> Ok great, now I just need to find some spare time...
>
>>> BTW, you will often have "meta" folders and files, think about the
>>> .git subdirectory or project files for editiors/ideas.
>>
>> I am not sure I follow how this is related?
>
> You were talking about the src and out dir "having parallel structure",
> but usually you have additional stuff in the src dir, like the examples above,
> if the user/IDE is particularly nasty you will find some recursive
> symlinks there.
>
>>> I find code "being pretty hairy" is a good reason for second guesses =)
>>
>> Paraphrasing a famous comment from Solaris, let's see you do better. ;-)
>
> There aint a perfect buildsystem until you do it yourself, right? =)
>
> Just to be sure, I wasn`t talking about the code quality, but it
> sounds like you
> attempt to solve a quite hairy problem, which I assume is some
> auto-magical detection of sub-projects and source-file globbing?
> The second guessing was about measuring up the pain that causes vs.
> the gain it brings.
>
> Kind Regards,
> Norbert