Charles Steinkuehler wrote
> What about the possability of moving forward with a mixed approach for
> the next major version?
>
> The core system (and most packages) could be compiled against uClibc,
> while packages that require it are compiled against a newer glibc that
> would optionally be installed by those with enough room (ie: running
> from HDD/flash/CD-ROM/etc).
I agree that it doesn't make sense to have two Bering distributions targeted
at the same hardware.
I propose to use Bering-uClibc for small (floppy-based) systems, while
moving Bering to a current glibc and targeting it at systems with at least
4M of disk (e.g. flash).
This approach would make it easier to compile stuff for Bering, maybe allow
to take binaries from other distributions. And at last I could easily build
Super-FreeS/WAN ;-)
Both distributions (uclibc and glibc) should only have different user space
binaries, i.e. they should have the same kernel, package structure,
configuration files and scripts.
The proposed distributions:
Bering-glibc Bering-uClibc
min. Storage 4M (Flash/HDD/CD) Floppy
C-Library glibc 2.3 uClibc
Devel Environment Standard Distro Special
- Alex
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
