On 2/7/02 at 9:35 AM, guitarlynn <[EMAIL PROTECTED]> wrote: (I had written:)
> > > After the make install is done, the LEAF system now has > > > /tmp/wget.lrp and an installed wget binary. Lynn wrote: > Then you have come up with how Debian now installs ..... a > set of one or more boot floppies, then 'wget' everything > else. I don't think you understand how it works. The ports tree is done after the installation. The ports tree is half-way between a packaging system and compiling on your own (though it is closer to the latter). For example, one wants to use ntop for example. You change into a directory /usr/ports/network/ntop, then do a make. The makefile checks for a pre-existing tar.gz file, and if it is not there, it goes to a series of FTP/HTTP sites looking for it, until it pulls down the source file. Then it unpacks, patches, and compiles. With a make install, it creates a package (for pkg_add in the case of *BSD) and installs it. Both the BSD Ports Tree and the Gentoo Portage system have dependency checking - if your compile depends on something, then that file is fetched (via FTP or HTTP), unpacked, compiled, packaged, and installed. My comment about scp was for a situation where you've downloaded and compiled on a full system, and want to install the package onto a remote LEAF system. With the appropriate keys in the right places, an installation of this sort could be (from the compile-time, full distro system): # scp ntop.lrp remote:/tmp # ssh remote -c apkg -i /tmp/ntop.lrp > The problem I'm seeing is that SF is going to _kill_ us if > we start mass compiling kernels on their systems I wasn't talking of SourceForge, nor of compiling kernels. Compiling kernels would be nasty - too many options. -- 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
