From owner-freebsd-ports@FreeBSD.ORG Tue Jan 2 22:08:33 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 447DB16A47C for ; Tue, 2 Jan 2007 22:08:33 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id BE35613C459 for ; Tue, 2 Jan 2007 22:08:32 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.8/8.13.8) with ESMTP id l02M8TsD029132; Wed, 3 Jan 2007 01:08:29 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Wed, 3 Jan 2007 01:08:29 +0300 (MSK) From: Dmitry Morozovsky To: Wesley Shields In-Reply-To: <20070102213427.GA97476@atarininja.org> Message-ID: <20070103010532.H28172@woozle.rinet.ru> References: <20070102215813.Y12293@woozle.rinet.ru> <20070102194013.GB95902@atarininja.org> <20070103000824.Y28172@woozle.rinet.ru> <20070102213427.GA97476@atarininja.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (woozle.rinet.ru [0.0.0.0]); Wed, 03 Jan 2007 01:08:30 +0300 (MSK) Cc: ports@freebsd.org, portmgr@freebsd.org Subject: Re: files to be checked on meta-ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2007 22:08:33 -0000 On Tue, 2 Jan 2007, Wesley Shields wrote: WS> > WS> > For some time I use local meta-ports referring different sets of useful ports. WS> > WS> > Most of the time, this works well; the only exception is meta-ports which do WS> > WS> > not install own files. WS> > WS> > WS> > WS> > I thought about refering /var/db/pkg/pkgname/ files, but this seems WS> > WS> > unscalable due to constant path changes. WS> > WS> > WS> > WS> > Your thoughts? WS> > WS> WS> > WS> I don't know if it's acceptable to look there but you can always use WS> > WS> ${PKG_DBDIR}/${PORTNAME} to get /var/db/pkg/portname (by default). I'm WS> > WS> not sure I understand the "constant path changes" you mention. WS> > WS> > Errm, this refers to current port, not to the dependency (say, my WS> > misc/ws-preferred wants to install x11/xorg) WS> WS> You're right. In the example you give above I would use WS> ${PKG_DBDIR}/ws-preferred which is what you mentioned in your original WS> post (and now makes sense to me, my apologies for the initial WS> misunderstanding). Though if your metaport name ever changes you will WS> have to chase it in other ports. WS> WS> I suppose one way to do it would be to have your metaport install a WS> "dummy" file that you can use for checking purposes in other ports. WS> This is easily done in a custom do-install: target. That's exactly what I'm thinking about. However, we should invent some consistent policy for this. What about touching category::origin file in some directory (in after-install phase)? Or even more, shouldn't this be a part of standard port installation process? I think this should be discussed with portmgr@, CC:ing them. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------