New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add apt to dpup, as a layer above the main SFS #2779
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I'm surprised at how complicated and pervasive these apt changes need to be......
neither pkg nor xbps (as in VoidPup) needed such extensive Woof-CE changes.....
On a philosophical point I think that initiatives like this that only affect a single build should use other Woof-CE "mechanisms" such as a specific specialized .pet to introduce just this feature and/or use of a pinstall in such a .pet or code in _00build.conf EXTRA_COMMANDS to achieve what is needed to incorporate the feature.
The changes are not that big - most of the diff is the addition of users and groups. woof-code/support/bdrv.sh, the only new file, is pretty short, and I think it's really clear. The customization of the Debian installation is needed to reduce its size, and prevent conflicts with Puppy. For example, the user must not VoidPup and any other Puppy that uses a foreign package manager will need the same kind of protection. After this explanation, do you still find this PR "complicated and pervasive" (quote)? EDIT: forgot to address this:
It's impossible. |
Interesting! |
No, spot works. (dpup has many applications running as spot and they all work; Firefox, PulseAudio and Blueman, among others, run as spot. But this is unsurprising, because the things that make spot work are all in the main SFS and always override the Debian configuration files). I added all users and groups defined in a clean Debian Packages with files that must be owned by a specific user or group can break, but only if these packages contain executables that run as non-root users (for example, the (apt needs the
Yes - for now, this feature only works with https://github.com/puppylinux-woof-CE/frugalify. puppylinux-woof-CE/frugalify@62e6efa changes the SFS sorting algorithm, so bdrv is below the main SFS, then everything else. For this "bdrv" concept to work with initrd.gz too, |
62383e6
to
56c3197
Compare
56c3197
to
a3e75e6
Compare
Done! Please review. I had to move some apt dependencies from devx to the main SFS, because the ISO images don't come with devx.
|
https://github.com/dimkr/woof-CE/releases/download/vanilladpup-9.9.9-apt/vanilladpup-9.9.9.iso Together with #2771: As you can see, it's possible to install 32-bit libraries and applications that rely on them, like Wine and Steam. |
https://github.com/dimkr/woof-CE/releases/download/vanilladpup-9.9.9-apt4/vanilladpup-9.9.9.iso Missing icons are back: Installation of Xfce after first boot of the ISO, without devx, works now: Xfce even works (and works under Xwayland!): After setting the GTK+ theme, icon theme and wallpaper it looks pretty usable: Same with KDE: And, the menu JWM is updated automatically and silently after every IMHO this PR is useful and complete enough to merge, and everything is optional and disabled by default. |
… into feature/dpup-apt
With 8a2d829 and 6c5f14e, all builds except dpup are unaffected by this PR. 72cc171 makes it safe to load bdrv above the main SFS, so it's unnecessary to change initrd to load bdrv first. All basic tests passed (VLC, GIMP, Xfce, KDE, gdm3, and now also LibreOffice): @peabee @mavrothal @01micko Objections? |
The wonders a small 19 MB SFS can do 😺