Moderator: Forum moderators
thanks dimkr
ok so much for that idea
how about running a build to the end with nothing in the main sfs file
then making each pet that would normally be added to the build an sfs file
and either symlinking or unionfs them to root with the empty main sfs
just ideas from a non guru
wanderer
It can be done, but i think it's too extreme.
If you want a modular Puppy, having stuff like libc and bash in separate packages means it will be very big on disk, because every package is compressed individually and most compression gains are from compressing package a and b together. And nobody wants to mess with core packages like libc and bash - every Puppy (or every distro that needs to be able to run shell scripts) must have them, so there's no reason to put them in separate SFS files other than the aesthetic aspect of this idea.
On the other hand, putting all the non-essential stuff (think, Ubuntu vs. Ubuntu if you tick the "minimal installation" checkbox during installation) in separate SFS files or one big SFS file makes sense because it allows the user to remove or replace some applications.
hi dimkr
so the main sfs will be the minimal core (with all the basic stuff)
and the other sfs will be the add ons (firefox etc)
wanderer
hi s243a and dimkr and everyone
so after some thought here is a proposal from a non guru
1 script to run a woof-ce build to the end
including just the pets that are needed for a shell
(pets a b c)
another script to squash pets into sfs files
to be loaded when desired either by unionfs or symlinks
(pets d e f) -basic x
(pets g h i) - window manager - jwm
(pets j k l) - rox)
(pets m n o) - xterm
(pets p q r) - geany
(pets s t u) - firefox
etc
that way you dont have to change anything in woof-ce
and can just use the scripts in the latest woof-ce
however since i cannot write the scripts
the point is moot
but it is an interesting intellectual exercise
wanderer