On 4/16/02 at 7:26 AM, Mike Noyes <[EMAIL PROTECTED]> wrote: > On Tue, 2002-04-16 at 03:46, David Douthitt wrote:
> David, > I think we should use the program's name, or place it in what RedHat > calls "Summary". Personally I prefer the deb format, but it doesn't > include summary/program name information. :-( Personally, I like the RPM (Red Hat) format :P > Program: Ultimate Packer for eXecutables = RPM Summary = DEB N/A > Executable: upx = RPM Name = DEB Package > Package: upx.lrp = RPM N/A = DEB Filename > > Debian packages provide the following information (apt-cache show): > Package, Version, Priority, Section, Maintainer, Depends, Suggests, > Conflicts, Provides, Replaces, Architecture, Filename, Size, MD5sum, > Description, installed-size. > > RedHat rpms have this summary information (rpm -q -i): > Name, Version, Release, Install date, Group, Size, URL, > Summary, Description, Relocations, Vendor, Build Date, > Build Host, Source RPM, License There's a LOT more than that - rpm -qi <rpm> only lists those things that are used by the current package. > Who determines what keywords and categories apply to each package? The creator of the package. > I believe these tags will cause confusion > if there is no set categorization template. I agree. Personally, I believe that: 1. A consistent standard is a good idea, and should be done. 2. A consistent standard will not be followed by all, and there will be some confusion. Go to http://www.rpmfind.org and do a look up by Group and you'll see what I mean. Look up by Distribution and it's similar. One thing I was thinking of - these *.desc files could (should?) be treated the way HTML is: an unknown keyword (matches the pattern /^[^:]*:/ ) causes a line to be ignored. So if someone suddenly started using a new tag ("Architecture: PPC" for example) then these lines would be ignored by current code. Also, to be able to ignore multiline tags, one should ignore all lines that start with a whitespace character after an unknown tag. > > > Name: Ultimate Packer for eXecutables > > > > Ouch! That's neither a program name nor a package name. > > The program is "upx" > > In my opinion that is the program name, while upx is the > executable name (see example above). Program: upx Summary: Ultimate Packer for eXecutables (UPX) ...and package name is: ${program}.lrp ...and <pkg>.version is: ${version}-${release} ...and so forth... > > > Version: 1.20-1 > > > > upx is not version 1.20-1 but version 1.20 (at least in > > this example). > > In your example, why did you indicate a release level of 1? Is the > release level different than the hyphen would indicate? A release level indicates the release of the package, and the version is the version level of the software. It could have just as easily been: Version: 2.54BETA20 Release: 2 ...like nmap - which leads to nmap.version being "2.54BETA20-2" -- 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
