Paul Jakma wrote:
> Choice #5: Explicitely list the dependencies in our packages, make our
> tools figure out what is compatible based on dependencies. I.e. the
> RedHat/Debian RPM/Deb model.
The RPM tools do this horribly badly. They always list the dependencies
as the selection of things present when the RPM was built. This forces
the admin to upgrade things outside the realm of what they were trying
to install, because the build machine was newer than the install
machine. The only way to get this right is to manually list the lowest
version of each dependency. It just doesn't work, for a large number of
reasons. Two of them are human error (how does one manually find all
the dependencies?) and test matrix explosion (I now have to test the
cross product of all version combinations).
--
--Ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ed.gould.vcf
Type: text/x-vcard
Size: 282 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20070322/d25145e7/attachment.vcf>
