Date: Mon, 10 Jan 2005 19:10:04 +0200 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: "Simon L. Nielsen" <simon@FreeBSD.org> Subject: Re: Makeing fetchindex really mirror INDEX Message-ID: <20050110191004.73fe13ab@it.buh.cameradicommercio.ro> In-Reply-To: <20050109185948.4470a02d@Magellan.Leidinger.net> References: <20050109143903.GC1187@zaphod.nitro.dk> <20050109174945.7f0353e4@Magellan.Leidinger.net> <20050109170219.GF1187@zaphod.nitro.dk> <20050109185948.4470a02d@Magellan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 Jan 2005 18:59:48 +0100
Alexander Leidinger <Alexander@Leidinger.net> wrote:
> At the time I wrote the first implementation of "fetchindex" it was
> supposed to be run at the time as "update". So the PORTSDIR has to be
> writable (except I've overlooked something). If this hasn't changed,
> there's no need for .CURDIR.
I would be extremely happy if we could have the INDEX-* file and all
associated things be able to use some other dir that PORTSDIR. This way
I could export /usr/ports over NFS and be able to build the INDEX
locally on each client. Is this already possible and I am missing it ?
Port tools already support this (e.g. portupgrade's PORTS_INDEX).
And a quick grep on ports/Mk/bsd.*.mk suggest that something like this
would be enough:
+ INDEXDIR?= ${PORTSDIR}
- ${PORTSDIR}/${INDEXFILE}
+ ${INDEXDIR}/${INDEXFILE}
And some of ports/Tools/* would have to be modified also.
--
IOnut
Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050110191004.73fe13ab>