jamesbond3142
commented
5 years ago On Fri, 29 Mar 2019 20:33:58 +0000 (UTC) wdlkmpx notifications@github.com wrote:
I've been slowly testing and updating the code that resides in woof-next.
It uses chroot and a simplified method to process packages, i like it, several times faster than the current stuff
I'm glad that you like it. I hope you enjoy reviewing / working with the code as I enjoyed when I wrote it :)
I tried to be as clean as possible, so if you have any questions, just ask. I may not be able to give immediate answer as it was from 5 years ago, but I'm sure sooner or later it will come to me, if it's really needed.
but it doesn't use pet packages, hehe... It's meant to build pups that use the compat distro package manager.
Just like you have intense dislike for ROX, I have intense dislike for PPM :)
So far i've been only testing and updating the woof-next slackware stuff, the deb-build stuff is probably completely broken.
Probably. Debian sid will be broken because Debian changed a lot over the last 5 years (and "sid" is basically the "leading edge"), e.g. systemd is just one of them.
The Ubuntu build, if Ubuntu still keeps its repo for Trusty, should still work. But I'm not sure if it's the case.
The current method in testing is handy for cross-builds between two different architectures, between puppies from 2 different compat distros.. but it's not that good if not doing a cross-build.
The current stuff is good for cross-builds, that's for sure, but a new alternate method should be implemented as part of the current build system based mostly on what i see in the woof-next branch.
Feel free to pick and choose stuff from woof-next, be it ideas, codes, etc.
Many hacks and packages-templates are still needed, well, at least a bunch of hacks.. an amalgamation of hacks could be applied after all the packages have been processed.
True. Woof-CE is basically two-in-one:
- It's a Puppy builder.
- It's Puppy base code, which is the "essence" of Puppy.
Woof-next only fixes (1); (2) is supposed to be fixed by the actual puppy builder using particular compat distro, and contribute it back to me for merging. But (2) never happened.
The current snapshot of (2) in woof-next was only good enough to boot to the desktop, but I didn't test beyond that. I was careful not to make too many changes because I wanted to track (2) with upstream (=testing), so all those extra hacks went into a separate package, which lives in lightofdawn.org/puppy-extra, if you want that I can send you those packages (the builders would have downloaded them anyway).
Enjoy.
-- James B
wdlkmpx
I've been slowly testing and updating the code that resides in woof-next.
It uses chroot and a simplified method to process packages, i like it, several times faster than the current stuff, but it doesn't use pet packages, hehe... It's meant to build pups that use the compat distro package manager.
So far i've been only testing and updating the woof-next slackware stuff, the deb-build stuff is probably completely broken.
The current method in testing is handy for cross-builds between two different architectures, between puppies from 2 different compat distros.. but it's not that good if not doing a cross-build.
The current stuff is good for cross-builds, that's for sure, but a new alternate method should be implemented as part of the current build system based mostly on what i see in the woof-next branch.
Many hacks and packages-templates are still needed, well, at least a bunch of hacks.. an amalgamation of hacks could be applied after all the packages have been processed.
Four possible SFS's
main.sfs devx.sfs doc.sfs nls.sfs
The need for chroot: so that post-installation scripts work properly,
"get rid of the multiarch symlink" should be merged and proper handling of deb packages should be implemented. etc.
These are just ideas, it's not hard for me to implement them, if time permits of course
The problem is dealing with somebody else's builds and stuff, this could happen in stages..
So this is something that could happen in the future. If time permits.