tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Problems with old "p5" packages and new "perl5" package

On Thu, 16 Oct 2008, Thomas Klausner wrote:

> On Thu, Oct 16, 2008 at 08:35:33PM +0200, Havard Eidnes wrote:
> > 1) Why, exactly, is this necessary?  If one follows the normal
> >    pkgsrc dependency rules, as is done by "make update" or the
> >    traditional or new pkgsrc bulk builds, when a package a given
> >    package depends on has been updated, you need to rebuild the
> >    package in question too.
> For the same reason that we bump PKGREVISION after shlib major change:
> If you don't bump PKGREVISION and see p5-Foo-1.0, how would you know
> against which perl it was compiled?
> If you have p5-Foo-1.0 and p5-Foo-1.0nb1 however, you can easily
> differentiate.

Does perl have a version when we know ABI may change? Maybe don't have a 
open-ended dependency, but have something like:

BUILDLINK_API_DEPENDS.perl+=    perl>5.10.0 perl<5.12.0

Guessing that 5.12.0 will be next ABI change. Is that doable?

Home | Main Index | Thread Index | Old Index