Charles Steinkuehler wrote: > I don't know that this is really necessary...most of the stuff we'd be > adding to the filesystem would normally reside in the 4 main > [/usr][/bin|/sbin] directories anyway...
Everything that goes into /opt would reside in those directories. What about nmap, for example? nmap.lrp is loaded at the same time that modules.lrp is loaded. > IIRC, /opt was for stuff you add to the machine at run-time, after install, > by compiling or some-such. However, the LEAF environment changes all that... As I understand it, /opt is for OPTional packages - so libc.so-2.2.1 doesn't count, but nmap does. > I would, however, like to see the packaging system be somewhat intelligent > about filetypes (binaries, config files, data directories, &c), ...that either calls for "magic numbers" or file extensions... > Yes, importing existing LRP files is a big "must-have" feature, especially > in the short-term. Support for a simple tar.gz file (ie no LRP meta-data) > might also be called for (anyone played with porting trinix packages to > LRP?). I've done it several times. It's rather simple, especially since the only thing needed is the LRP /var/lib/lrpkg/<pkg>.* files... > The 64KBit (oh wait, it's the 21'st century...) The 64MBit question is what > gets stashed in the tar wrapper, and what goes in the tar.gz file inside the > tar wrapper. I think it's obvious a crypto signature needs to be in the > external wrapper...anything else that HAS to be there, or would be amazingly > convinent? I'm also thinking about slow systems, so any add-ons should come > before the big tarball file, and we may want any bits of information > required to decide exactly what to do with the package available without > un-gzipping the internal tarball. Anyone know if busybox tar is smart > enough to stop reading the file when it finishes reading the file you > requested? It seems like it should be, what with tar being the "Tape > ARchiver"...you don't want to read your entire tape if you're just restoring > a 2K file found at the beginning... A tape has a header and inter-file gaps, as I remember. You can specify which file you want, and it skips over the others. I used to use magtape - still have a few for one I get a magtape reader :) Why bother with the odd tacking onto the end? To me, I'd say just creating a tar.gz file like so: <pkg>.srp contains: <pkg>.lrp <pkg>.asc ...would be enough. There's nothing else that should be outside the *.lrp archive. The only reason the signatures have to be outside is that they need to work with the archive itself. One doesn't need to determine what to do with the internal archive: it's a *.lrp, you install it. Otherwise, if you just want the *.asc file: PKG=nmap tar xzvf $PKG.srp $PKG.asc ...should get you the package signature. If you want, you can even archive the signature first so that it occurs first in the file - and thus the entire file doesn't have to be read to get the signature out. At least, I assume that would be the case - but would it? I can't tell... > It's looking like the -O option to tar (and supported by busybox) is going > to start being very handy... Not sure how. You just extract the file to stdout, then what? Which file? Why? _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
