Re: enforcing pkgsrc/category/$PKGBASE

[David Brownlee <abs%NetBSD.org@localhost>]

On Thu, 19 Feb 2009, Takahiro Kambe wrote:

> In message <alpine.NEB.2.00.0902181736560.2542@localhost>
>         on Wed, 18 Feb 2009 18:16:24 +0000 (GMT),
>         David Brownlee <abs%absd.org@localhost> wrote:
> >          The flies in this proposed ointment are:
> >              a) *-devel packages which provider newer compatible versions
> >                 of a base package
> >              b) ap2?-* packages which can generate apache 1.x 2.0 or 2.2
> >                 packages
> >              c) py-* packages, which generate different output packages
> >                 based on the version of python installed
> ruby-*, zope-* and php-* packages, which have similar situations with c).

        But they all fit a fixed pattern. What do you think of any
        such packages having to set PKG_MULTIVERSION=python or similar
        (in most cases that could be set in a common file they include)

--
                David/absolute       -- www.NetBSD.org: No hype required --