Subject: The PKGREVISION bump after openssl bump
To: None <email@example.com>
From: Todd Vierling <firstname.lastname@example.org>
Date: 11/17/2003 09:22:39
I can see that the security/openssl version was bumped. However, the new
version is completely binary compatible with the old version (there's not a
single PLIST changed, nor is there any _NEED_NEWER_OPENSSL criteria change
So why were all the dependencies bumped? If you're worried about binary
package autoinstalls, remember that they will get the newer version
automatically if it exists within the same binpkg repository.
This policy about bumping PKGREVISION recursively on *any* version change is
starting to get on my nerves, and I'm sure I'm not the only one. Bumping
dependencies' PKGREVISIONs should only happen if there is a binary
incompatible change of some kind.
-- Todd Vierling <email@example.com> <firstname.lastname@example.org>