Hi Gavin,
Did you get the mail last night?
If not, I can try again. It was very small in the end!
I did get the mail, but it didn't contain a patch. I guess you didn't
get my response to that (sent to your other account) ;-)
Correct. We _have_ to move sooner or later, because we'll hit more and
more packages that simply won't compile anymore with the old uClibc
version (so far, we've managed to patch our way around that, but
there'll be a point when that's impossible).
Indeed. Related to that, it possible that effort will be wasted coding
round problems that could have been resolved in moving to the later
version.... It's just a question of working out where the breakeven point
of effort is.
Right. And often it is easier (or rather, the risks are easier to
control) to have to work on one specific package so it will compile
against an old uClibc, than switching to a new uClibc and having to make
sure everything still compiles and works (the latter is obviously more
difficult, since that requires a lot of testing - and some of the
packages that were built upon request by users aren't even used by
anybody in our group, so it's extremely hard to test those).
And then, the newer versions also offer additional features (like the
NPTL support that's currently being worked on).
The new feature around the corner! I also think a new libm is expected as
well. However, will we be able to use NPTL without a 2.6 kernel?
Well, RedHat made it work with RedHat 9 and Fedora Core 1, so it is
possible - but I don't know if NPTL support is there in the vanilla kernel.
Plus will
it actually be that useful for what these systems do?
Good question - but I've given up thinking about that a long time ago -
different users come up with different usages for LEAF (just look at the
list of packages we provide - there are quite a few that I'd never even
let come close to my router ;-)). But since not every LEAF installation
is a router, it's ok with me to at least test if those new features can
make it into Bering uClibc (within reason - we're not willing to waste
too much space just to add a new feature hardly anybody will use).
Martin
--
You think that's tough? Try herding cats!
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
