I finally came to realize what the confusion I was feeling was - especially in reference to sources that are used IN a base LEAF system. I had been considering three different methods of creating packages or binaries:
* Create a directory in the source tree (lrp/) and do a make in this directory. This works well to create packages... * Put in a makefile in a directory all by itself, with patches. A make then pulls the source code from the network as needed and creates a package... This is good, and also makes for very small source tree - no archives, no original sources - just makefiles and patches. * A variation on the last that creates not packages but binaries - and which DOES contain source code. What it comes down to is the following FreeBSD entities: * making packages (*.lrp) * ports * source code for the system I've started creating a directory tree - in preparation for putting it into CVS - a tree that contains configurations, patches, etc - just for creating binaries that are used by Oxygen itself (and not packages or ports). Once I get this done (about a dozen archives or so) - I'll put them into Oxygen (all will then use glibc 2.1.3 if not static) - and put the tree into an Oxygen development CVS tree. I'm excited about the "ports tree" as well. The ultimate would be to have an NFS-enabled busybox mount that would allow a user to boot a LEAF, then mount the device over NFS - then perhaps do a make which gets the archive, compiles it in that OTHER environment, creates a package, installs it to LEAF, and perhaps even backs it up... Perhaps one could do this with a Network Device (/dev/nd0)...? -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
