Hi Olaf, On 15/2/22 9:26 am, Olaf Buddenhagen wrote: >> I could create a github repo that contains everything for rump in one repo, >> but it would take time and would be easier to do once the netbsd src patches >> are upstreamed, so we would not need to maintain separate patches. > > Admittedly without having followed what you actually did there, I have > to wonder: why would in be easier? Isn't a Git branch the obvious way to > manage non-upstream modifications?...
Yes, that is the usual way to manage changes, but the entire NetBSD source tree is very large, and we only have about 100 lines of changes in total that I am trying to upstream. So I propose we use a submodule for their untouched source tree and just keep a patch, until that is upstreamed, then one day we can just use their tree as-is. The debian package is bloated because the tree is committed as source and patches are also maintained in a folder, so the worst of both worlds. Damien
