Date: Tue, 2 Jan 2007 16:34:27 -0500 From: Wesley Shields <wxs@atarininja.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: ports@freebsd.org Subject: Re: files to be checked on meta-ports Message-ID: <20070102213427.GA97476@atarininja.org> In-Reply-To: <20070103000824.Y28172@woozle.rinet.ru> References: <20070102215813.Y12293@woozle.rinet.ru> <20070102194013.GB95902@atarininja.org> <20070103000824.Y28172@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 03, 2007 at 12:12:00AM +0300, Dmitry Morozovsky wrote:
> On Tue, 2 Jan 2007, Wesley Shields wrote:
>
> WS> > For some time I use local meta-ports referring different sets of useful ports.
> WS> > Most of the time, this works well; the only exception is meta-ports which do
> WS> > not install own files.
> WS> >
> WS> > I thought about refering /var/db/pkg/pkgname/ files, but this seems
> WS> > unscalable due to constant path changes.
> WS> >
> WS> > Your thoughts?
> WS>
> WS> I don't know if it's acceptable to look there but you can always use
> WS> ${PKG_DBDIR}/${PORTNAME} to get /var/db/pkg/portname (by default). I'm
> WS> not sure I understand the "constant path changes" you mention.
>
> Errm, this refers to current port, not to the dependency (say, my
> misc/ws-preferred wants to install x11/xorg)
You're right. In the example you give above I would use
${PKG_DBDIR}/ws-preferred which is what you mentioned in your original
post (and now makes sense to me, my apologies for the initial
misunderstanding). Though if your metaport name ever changes you will
have to chase it in other ports.
I suppose one way to do it would be to have your metaport install a
"dummy" file that you can use for checking purposes in other ports.
This is easily done in a custom do-install: target.
-- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070102213427.GA97476>