Tiny Core Base > Final Releases
Tiny Core v4.0
bmarkus:
--- Quote from: curaga on September 25, 2011, 12:55:32 PM ---GCC was rebuilt with the frame-pointer option turned on, current 4.x toolchain should create normal sized executables again.
--- End quote ---
gnutls is even smaller, 483k -> 471 k with same build script! :)
bmarkus:
A while ago it was decided to drop openssl-0.9.8 and move to 1.0.0 How do we proceed?
Just built bind against 1.0.0 static. It's OK, but in general I prefer shared libs to reduce size and do not want to maintain dependencies.
Jason W:
openssl-0.9.8 has not been dropped, it is still the standard shared openssl. The static openssl-1.0.0 was made available for folks who want to build their apps against the latest openssl, without causing conflict with the shared openssl-0.9.8.
The benefits of going static with openssl is we never have to have a repo wide rebuild to accomodate an openssl upgrade. Or at least it buys us time until we want to rebuild everything against a new latest shared openssl.
Perhaps with TC 5.0 will be a good time to start from scratch, with by then a gtk3, python3. openssl-1.x, etc. With openssl being the only thing that needed a repo wide rebuild, and it affects the most extensions of any of the three libs mentioned above, we are just staying with 0.9.8 for the shared lib. For now, smaller size versus latest and greatest, the extension maker has a choice.
But to be honest, I personally like the idea of a static openssl since then we would never have to rebuild the entire repo for an openssl upgrade. The cost being extension size. Further discussion can take place in the thread below:
http://forum.tinycorelinux.net/index.php/topic,11058.0.html
andrewb:
Are there any files that may be backed up that need to be modified / removed when upgrading a 3.8 installation to 4.0?
Just a suggestion, but maybe a standard section in any release announcement could be files that will be affected that amay be in the backup, e.g. in the announcement of 3.7 there was:
--- Quote ---Note: Files that have changed and are likely in your backup:
--- End quote ---
Perhaps 'Files that have changed and are likely in your backup:' could be made a standard section, even if it just stated 'None'. This way users could be sure that the issue of files in the backup isn't overlooked when upgrading.
maro:
I just noticed that the downloads page is still pointing to the v3.8.4 images. I'd imagine as soon as the MultiCore ISO has joined it's "siblings" those links will be adjusted accordingly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version