Date: Mon, 13 Sep 2004 15:28:20 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Dan Langille <dan@langille.org> Cc: freebsd-vuxml@freebsd.org Subject: Re: Matching a name to a port Message-ID: <20040913202820.GC73780@madman.celabo.org> In-Reply-To: <20040913160315.C22240@xeon.unixathome.org> References: <20040913123610.G22240@xeon.unixathome.org> <20040913174748.GC71191@madman.celabo.org> <20040913135431.F22240@xeon.unixathome.org> <20040913183627.GG71191@madman.celabo.org> <20040913144103.U22240@xeon.unixathome.org> <20040913190509.GK71191@madman.celabo.org> <20040913160315.C22240@xeon.unixathome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 13, 2004 at 04:21:01PM -0400, Dan Langille wrote:
> On Mon, 13 Sep 2004, Jacques A. Vidrine wrote:
>
> > On Mon, Sep 13, 2004 at 02:56:10PM -0400, Dan Langille wrote:
> > > FreshPorts knows nothing about ImageMagick-nox11 because there is no such
> > > port. It knows only about ImageMagick, against which commits are made.
> > >
> > > Proposed approach for FreshPorts: I think FreshPorts will ignore package
> > > entries for which it cannot find a corresponding port. If all packages
> > > for a vuln fail to relate to a port, that will be something which
> > > justifies further investigation.
> >
> > I think that is a reasonable approach.
>
> FYI, I just realised that FreshPorts can only determine the
> ${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX} for existing ports. This will
> exclude ports which have been deleted. Those values aren't easy to grab.
Right, thus my several allusions to a non-existent "package name
history" database. :-)
Cheers,
--
Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040913202820.GC73780>