Re: Updating the hurd in Guix

2022-02-16 Thread Samuel Thibault
Olaf Buddenhagen, le mer. 16 févr. 2022 05:14:31 +0100, a ecrit: > Putting it more bluntly: so the NetBSD source tree is large... And? And it's a pain in the ** to work with. While using dh_quilt_patch is a very common way to work in Debian packages. Yes, that's Debian-centric, but we're at very

Re: Updating the hurd in Guix

2022-02-15 Thread Olaf Buddenhagen
Hi, On Tue, Feb 15, 2022 at 01:59:11AM +, Damien Zammit wrote: > 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. [...] I feel like I've heard this story

Re: Updating the hurd in Guix

2022-02-14 Thread Damien Zammit
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

Re: Updating the hurd in Guix

2022-02-14 Thread Olaf Buddenhagen
Hi, On Sat, Feb 12, 2022 at 11:28:03PM +, Damien Zammit 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.

Re: Updating the hurd in Guix

2022-02-12 Thread Damien Zammit
Hi Ricardo, On 11/2/22 11:58 pm, Ricardo Wurmus wrote: > I still haven’t been able to upgrade the Hurd packages in Guix because > it is not clear to me what commits and additional patches we need — and > I don’t have enough time to figure this out by myself. Yes I think we need an upstream for

Updating the hurd in Guix

2022-02-11 Thread Ricardo Wurmus
Damien Zammit writes: > On 11/2/22 3:42 pm, jbra...@dismail.de wrote: >> Way to go Damien for his 1st Fosdem GNU/Hurd presentation, which he nailed >> by the way! It was an >> awesome presentation! If you haven't seen it yet, then you should check it >> out here: >> >>