On 16/09/2019 13:53, Christoph Badura wrote:
On Mon, Sep 16, 2019 at 12:25:00PM +0000, Antti Kantee wrote:
On 14/09/2019 18:14, Christoph Badura wrote:
In my guest to update rumpkernels to current netbsd sources I've hit the
following snag:
NetBSD tools now builds pax. So I moved it in listsrcdirs from "usr"
to "sys" and did a githubdate in my own testing for of src-netbsd.
NetBSD tools has ~always built pax. Did it get moved away from under
TOOLS_BUILDRUMP=no for some useful reason or by accident?
It didn't occur to me to investigate that. I just checked and it was.
So, should I check the changes to tools/Makefile since your last githubdate
and figure out which of the additions are really necessary for buildrump.sh
and exlude the others under TOOL_BUILDRUMP=no instead?
In my opinion it's enough to investigate only when things break. Most
(all?) of the unnecessary tools' sources aren't present, and even if
they are, accidentally building an extra small tool which accounts for a
fraction of a fraction's fraction of the build time isn't the end of the
world.
A smaller change would be to reverse the order of the branches in the
mergeing, i.e. "git merge posix-source user-src kernel-src". That would
allow to migrate additions from user-src -> posix-src -> kernel-src, I
think. But all-src and buildrump-src currently have posix-src and
user-src in different order. That makes me less optimistic, that that
approach could work.
Can't recall if there was any magic/logic to the order. I don't really
have special love for the branches. They're more like a well-meaning
experiment, and if they get in the way of accomplishing something, they
might as well be removed entirely.
