On Sat, 2002-08-24 at 20:42, guitarlynn wrote: > I've been doing some thinking about a good way to setup the > LEAF src tree, as there is still nothing there. <snip>
Lynn, Thank you for opening this topic for discussion again. :-) Remember I'm not a programmer when reading my comments below. > src +bering > +dachstein > +oxygen > +packetfilter > +wisp-dist Agreed. I'm with you so far. > +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. If we use David's build system for our packages tree, isn't the glibc separation unnecessary? http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/devel/ddouthitt/base/ Has anyone evaluated David's build system yet? I'm sure he would appreciate some feedback. Is it a usable system for our packages tree? > 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. Please explain the need for a binary tree in src. Its purpose is not clear to me from your explanation above. Is it for source tarballs from other projects? > Any thoughts, as we need to have the src tree up and populated! Agreed. We have discussed this tree for over a year now, and little has come of it. We can't cooperate effectively on releases/branches or packages until we have a working src tree. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ------------------------------------------------------- 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
