"Angelacos, Nathan" wrote: > > Jack Coates <[EMAIL PROTECTED]> wrote: > > >And for this reason I'm thinking that versioning in the filename is a > >convenient nice-to-have.
It would. But with an 8 character limit, what about programs like nmap, which is has version numbers like 2.3BETA10 - which is 8 characters if you take you the '.' :( > >If the version and author attributes are kept > >on the web server that should be enough to enable accurate downloads, > >though there are still troubleshooting issues. Determining what version > >an end-user is using will require looking at package sizes. I did up a Perl script to read a package's <pkg>.desc (description) file and produce web pages. The script is at /pub/oxygen/webdesc, and example files are at /pub/oxygen/upx.desc (to be included in a package *.lrp) and /pub/oxygen/upx.html (the end result). I must admit I've been sloppy; my packages haven't been getting *.desc files as they ought... > Does anyone see any advantage to adding some packager/versioning information > inside the /var/lib/lrpkg/<pkgname>.version file? I think the file is > supposed to have the package version number. What if a second line had the > packager's name/version/tag/vfat package name/whatever. This would cause problems for lrpkg and apkg which both figure the file for one line... > Scripts that use the file to get the version number would have to grab just > the first line, but putting the additional info in the file would allow the > original package info to be saved even if the target system was a fat-only > box. True - but it also is bad since the file is for VERSION information; the *.desc file (description) is, I would think, a good place to go - and extensible - and doesn't break package programs. Even if you updated apkg and lrpkg, old versions would still break. Going to glibc 2.1 and 2.2 is bad enough :) > Just a thought. And a good one. It's about time us package creators got to this... Here's the keywords my script understands: keywords["Name"]=1 keywords["Version"]=1 keywords["Release"]=1 keywords["Packager"]=1 keywords["Packaged"]=1 keywords["Keywords"]=1 keywords["Description"]=1 keywords["URL"]=1 keywords["License"]=1 keywords["Group"]=1 ....and predefined licenses: licenses["GPL"]="http://www.gnu.org/copyleft/gpl.html" licenses["GPL2"]="http://www.gnu.org/copyleft/gpl.html" licenses["LGPL"]="http://www.gnu.org/copyleft/lesser.html" licenses["MIT"]="http://www.x.org/terms.htm" licenses["X11"]="http://www.x.org/terms.htm" licenses["MIT/X"]="http://www.x.org/terms.htm" licenses["X"]="http://www.x.org/terms.htm" licenses["BSD"]="http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5" licenses["Artistic"]="http://www.perl.com/language/misc/Artistic.html" licenses["Mozilla"]="http://www.mozilla.org/MPL/MPL-1.1.html" licenses["Netscape"]="http://www.mozilla.org/NPL/NPL-1.0.html" licenses["MPL"]="http://www.mozilla.org/MPL/MPL-1.1.html" licenses["NPL"]="http://www.mozilla.org/NPL/NPL-1.0.html" licenses["QPL"]="http://www.troll.no/products/download/freelicense/plaintext.html" licenses["Qt Public License"]="http://www.troll.no/products/download/freelicense/plaintext.html" licenses["PHP License"]="http://www.php.net/license/2_02.txt" licenses["PHP"]="http://www.php.net/license/2_02.txt" licenses["OpenLDAP"]="http://www.openldap.org/software/release/license.html" licenses["IBM"]="http://oss.software.ibm.com/developerworks/opensource/license10.html" licenses["IBM Public License"]="http://oss.software.ibm.com/developerworks/opensource/license10.html" licenses["FDL"]="http://www.gnu.org/copyleft/fdl.html" ...and the example upx.desc: # This is a first try at a description file <pkg>.desc # # These comments should be ignored; in fact, any line # that does not match a known keyword should be ignored; # but don't tell anyone I said that.... :-) # # There is the potential, too, to create a HTML-generator # that reads this file and creates a web page: you could # even make this file executable and put a #! line at # the top. Then creating a set of web pages could be as # simple as: # # -- unpack all description files # # for i in *.lrp ; do tar xzf $i var/lib/lrpkg/*.desc ; done # # -- Run all files # # cd var/lib/lrpkg ; for i in *.desc ; do eval $i ; done # # ...You could even do it in a running LEAF system, and create # web pages from it... Name: upx Version: 1.20 Release: 1 Packager: David Douthitt <[EMAIL PROTECTED]> Packaged: Wed Jul 18 09:40:25 CDT 2001 Keywords: compressor compress Description: Use UPX to compress executables and kernels even smaller! URL: http://upx.sourceforge.net/ License: GPL2 Group: Utilities/Compression Any reason I shouldn't run with this and go nuts in my package directory with new *.desc files? _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel