Charles Steinkuehler wrote: > Or yet another config file...Actually, I see this as an extension of the > package file list. There needs to be support for paritally backing up > files, which means some rudimentary knowledge about which files are > user-changeable, and which are not.
Those in <pkg>.conf are user changeable; those not in <pkg>.conf are not... > Maybe even standardizing on including > md5 sums so package integrety could be checked and/or only modified files > could be backed up. # Find every file modified in the last $DAYS days... and back up busybox find / -mtime -$DAYS | xargs tar czvf newfiles.tar.gz > > I've done it several times. It's rather simple, especially since the > > only thing needed is the LRP /var/lib/lrpkg/<pkg>.* files... > > Cool...maybe the process could even be automated... The lrp-diff files do this automatically for a large part. The Trinix tarballs have *NO* "metadata" at all.... pure binaries. > OK, so nothing but a crypto sig outside the wrapped extended-format-LRP > format tarball. Now what extensions go INSIDE the LRP+/LEAF/whatever > tarball file? > > Any suggestions for the extention on the internal tarball? I vote for .leaf To me, there'd be two files: <pkg>.lrp and <pkg>.asc - and then the "extensions" would all be in the metadata contained within *.lrp. I'd go for *.srp (Secure LRP) or *.laf (LeAF) for the new extension (visible at the end of the process). Internally, the *.tar file would have no name (stdin), and the two files contained in the *.srp would have a *.lrp and a *.asc. > > Not sure how. You just extract the file to stdout, then what? Which > > file? Why? > > I was thinking: > > tar -xfO <package>.leaf <package>.tgz | gunzip | tar -x > > I'd prefer not to keep duplicates of the internal tgz file around, for > systems low on space. How about: ( cd / ; tar xzOvf <pkg>.leaf <pkg>.lrp | tar xzvf - ) Problem is, this introduces special handling for these new files. Better yet (but more memory) would be: tar xzOvf $PKG $(basename $PKG .leaf).lrp > /tmp/$(basename $PKG .leaf).lrp PKG=/tmp/$(basename $PKG .leaf).lrp ...or something of that sort. Then there'd not have to be any new code weaved in, only a "preprocess" to get the *.lrp. A signature verification could go here, including a *.md5 sum... _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
