big_bass wrote:maybe I am crazy after all I could just do an another update of TXZ but the future apps will need an updated glibc
I started the work of splitting packages for a test build this is not a rush job
I dont care how long it takes but I do care about doing it right
... Joe
I have been using glibc-2.12.1 with a -Os patch (and a couple sed scripts to force the issue) that I derived from the commit that broke -Os, but have just been using the default values for glibc and kernel version compatibility. Should these be set to an early version to keep better compatibility with existing binaries or disabled altogether for the smallest, fastest code. (Note that including earlier versions _ADDS_ workaround code => larger,slower)
btw I prefer busybox tools and simple slackware style packages (if only busybox had squashfstools I'd be set)
... to download a list of user selected packages (using short options, but busybox wget doesn't have -B or -i options)
with wget-FULL this could be
wget -c -t 0 -B $MIRROR -i packages_selected.txt
but with busybox wget:
for package in `cat packages_selected.txt`; do wget -c $MIRROR/$package; done
The big difference is that the busybox code will require much less modification if you need to add mirrors, packages,chksum validation etc... and it works with wget-FULL as well.
but it is not always the case that busybox versions requiere the extra code
... to install a .txz, busybox will autodetect the compression type now:
tar -xf /path/to/package.txz -C /
#works for tar.gz tar.bz tar.xz tar.Z tar.lzma (regardless of file extension)
#thus saving a nest of case statements if you support multiple types
The simpler the better. I try to avoid optimization that comes at the expense of simplicity if it can be avoided.
The more complexity that gets added, the harder it is to maintain/fix (such as supporting 10+ different install methods that you don't personally use ... or 100 languages that you don't speak, or 1000s of hardware that you don't have)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].