Hi Janneke, On 20/6/23 06:00, Janneke Nieuwenhuizen wrote: > The rumpkernel archive is ridiculously large. It manages to grow so big > mainly by adopting the evil practice of bundling other packages. The > archive contains copies of many GNU utilities, a copy of llvm, and even > a copy of postfix. > > The archive can most probably be pruned a lot further without > consequences, but this is a helpful start. I'm built the Guix > rumpkernel using this pruned archive and it works fine. The same list > of librump* libraries are built and there are no messages in the build > log that suggest things are missing. > > Because the patches are so big I'm only sharing the prune.sh script that > will create some 'prune: ...' commits.
I took your prune.sh script and modified it to just remove files. I could not easily see if there were more things to prune. I then rebuilt the tree from scratch by adding files from existing repo on upstream commits to a blank repo, and running the prune.sh script before committing in the new repo for each upstream commit. Then I imported the rest of the patches preserving authorship. Finally I ran git gc. I think everything is rebuilt as before, but the bare repo is only 114M now. Samuel, can you please see if this new repository is suitable to replace the debian rumpkernel: http://git.zammit.org/rumpkernel-debian.git I have added 3 extra commits in develop branch (that perhaps could also be merged to master). Thanks, Damien
