I'm curious - what makes you think so? My day work is "targeting enterprise use" (so, I think I know what they'd ask for, but then, different customers ask for different things, so one can't be sure), and with Bering uClibc, I don't see any of the "buzz-words" that would make it in the enterprise world (like SLAs, for example). Maybe my perception of Bering uclibc is very different of yours - and if that's so, I'd be curious to hear yours.Now a survey ???
What would be the advantage and drawbacks of merging the Bering & Bering-uclibc distributions ? What would be the advantage and drawbacks of keeping the Bering & Bering-uclibc distributions separate ? IMHO, I think that we don't need 2 separate variantes of bering. What do the others "gurus" think about that ???
Etienne, The main difference I see between the Bering branches is the target audience. The uClibc team is targeting enterprise use, while the Bering team is targeting SOHO/end users.
Martin
------------------------------------------------------- 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
