This seems to be about the same as what was proposed last time this thread went around. I think this solution makes perfect sense. It has my vote!
Regards, Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of guitarlynn Sent: Saturday, August 24, 2002 11:43 PM To: [EMAIL PROTECTED] Subject: [Leaf-devel] cvs src tree I've been doing some thinking about a good way to setup the LEAF src tree, as there is still nothing there. As I need to upload my own src for a package binary and working on others, I need somewhere to put it within the tree. My thoughts on a tree structure are as follows: src +bering +dachstein +oxygen +packetfilter +wisp-dist +packages +glibc-2.0 +glibc-2.1 +glibc-none +binaries I believe the seperation of glibc within packages will avoid confusion between packages with the same package name that actually differ in end use. The addition of a binary tree will allow for compiled executables/utilities that are not part of any core image or package that are available for LEAF. Any thoughts, as we need to have the src tree up and populated! -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel