On Thu, Jun 12, 2003 at 08:34:49PM -0400, Jim Wise wrote:
> Is there a reason the ability to explicitly version system packages was
> discarded?  Previously, a system package on a release branch was
> versioned with the current OS version of the branch, plus a `tiny'
> version number of the syspkg, such as
> 
> 	base-util-bin-1.6.0.0
> 
> for the version of that package that shipped with 1.6.0, and
> 
> 	base-util-bin-1.6.0.1
> 
> for a hypothetical first `relevant' update to that package (such as when
> an SA was issued for a binary in the package).  This allows tracking of
> `important' changes in such a syspkg, much like the `nbXX' version
> add-ons in pkgsrc.

The old versions don't work at all well on -current, and anything
which discourages people from running the -current branch should be
discouraged, IMO.

The old versions numbers were coming out as 1.6T-0. This is too
large a granularity, and are not at all friendly.

The date-based versioning has worked fine for us in pkgsrc - that's
how the versions required are all calculated and used.
 
> regpkg and regpkgset are very nice, and address a very real
> maintainability issue with the old code.  _But_ I think this feature
> should not be lost.
> 
> Barring any objections, I'll put something together to re-add this
> functionality, and either commit it, or mail it off to you.
> 
> Sound good?

No, please see my previous reasons.

Regards,
Alistair