On Mon, Aug 07, 2000 at 12:15:49PM -0400, Jeff Johnson wrote: > 1) dependency resolution, of both build and install varieties. > rpm packaging is as good (or as bad) as the dependencies > are. What's unfortunate, at the moment, is that the only > way to get dependencies correct in a package is by looking > at a full universe (read: complete set) of distribution install > dependencies. That also only works for a single distro, however, > as each distro uses sligltly different dependency glue. Hmm. I just visited the URL and I thought about the "standard package name" stuff. Is it really that difficult to get right? I mean, we already have a group thats just in the right position to define the 'right' package name and the 'right' way to package: The software developers. To sum it up: Wouldn't it solve a lot of problems if the software developer, instead of the distributor, provided the "official" package? Of course, distributors could still do things like put patches in and create a custom-tailored default configuration, but that shouldn't really change things like dependencies and path names. Whad'ya think? Regards ---Ingo Luetkebohle / 21st Century Digital Boy its easy to stop using Perl: I do it after every project
Attachment:
pgp00002.pgp
Description: PGP signature