To quantify, here are the compressed package sizes before and after my recent splurge:
xorg_xorg_servers-73 1.42MB 2.24MB
linux_kernel-220.127.116.11 24.17MB 24.80MB
So, the total increase attributed to these two is 1.45MB.
I will revisit that Xorg package and take out some of those support files that I had put in. I didn't know whether the extra drivers needed them -- well, I'll assume they don't. Testers will soon pick up something wrong in the error log if a driver won't load.
The kernel package is massive. For 516 I think that I will build the live-CD with a separate 'zdrv'. In cases where the 'pup4-416.sfs' main Puppy SFS file copies into RAM, this is going to reduce the footprint in RAM considerably.
Comments:Posted on 26 Jun 2009, 11:30 by dogone
Keeping Puppy under 100MB is laudable, but I wouldn't sacrifice any key features in the process. Puppy should remain close to the magic number, but if another meg or three buys real value for the user, I say go for it.
Posted on 26 Jun 2009, 13:16 by adi
Perhaps for most computers made after 2000 the space is not a problem. I upgraded my memory to 1G both for puppy and puplets. I think the speed must remain the same but the space can be increased as necessarily. Only old laptops remain a problem...
Posted on 26 Jun 2009, 14:47 by ttuuxxx
Hi Barry a lot of the Libs in 415 weren't stripped, that alon would bring it under 100MB, /usr/lib/libgtk-x11-2.0.so.0.1400.7 reduces over 700kb smaller if its stripped.
I'll edit the sfs later and strip them all :)
Posted on 26 Jun 2009, 14:47 by 01micko
100 is just a number. Apps get bigger, fixes add size, a few meg is forgivable.
pCD, a cd player by zigbert works well on older kit as well as new.
3kb. Don't know if you missed it. There is no simpler cd player for puppy. Necessary IMHO.
Posted on 26 Jun 2009, 19:30 by ICPUG
100MB is just a number
Maybe, but perhaps it should be a requirement.
Once you allow 101 then 105 becomes acceptable and then 110 and then ...
The 100MB affects all sorts of things - download time, bootup time, amount of RAM required to runin RAM, ratio of tight code to sloppy code in particular.
The unique selling point of Puppy is what it can do in 100MB.
When it is impossible to fit the essential requirements into 100MB we may have to consider an increase. However, 'it is just a number' is no justification.
Posted on 26 Jun 2009, 23:20 by zigbert
Which apps depends on the flac lib. I wonder because 'ldd ffmpeg' doesn't show flac as a dependency. If that's true it should be doable to write a ripper without flac (216kb), cdparanoia (43kb) and maybe libcddb (31kb). Pmusic and Pburn supports *.flac via ffmpeg.
Posted on 28 Jun 2009, 16:04 by BarryK
Ffmpeg normally uses external shared libraries where possible. Probably when ffmpeg was compiled, there was no libflac available so it used it's internal flac library.
Ripoff and Asunder use libflac. If I recompile ffmpeg it too will probably use libflac. ...I'll have to check that out.
Posted on 28 Jun 2009, 17:39 by zigbert
I'll put the mini-dependent ripper on hold, and wait for your decision....