Mike Noyes wrote:
Nice work - that should make the links for pointing people to the right package a lot shorter (and hopefully solve the problems with slow CVS servers).Everyone, Our binary packages directory[1] in cvs is now exporting daily to our shell space on SF. I haven't completed population of glibc-2.0[2] or nolibc yet. Also, I haven't worked out how I want to auto index our package repository. Anyway, you can now link to any of our current packages from:
http://leaf-project.org/packages/
As always, comments and suggestions are welcome.
But for this to be really useful at least for the Bering uClibc team, we don't only need the packages from leaf/bin/packages/uclibc but also the ones from leaf/bin/bering-uclibc/packages (since that directory contains the packages that are specific to Bering uClibc, but not specific to a uClibc version).
I guess one needs to be careful to not export the whole leaf/bin/bering-uclibc/ tree (since that would result in exporting disc and iso images - and that would probably make us blow the quota we have for the shell server).
Do you think also exporting leaf/bin/bering-uclibc/packages would be possible? If so, I'd change our packages page to reflect the change ASAP.
Thanks
Martin
-- You think that's tough? Try herding cats!
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
