Date: Mon, 1 Aug 2011 19:21:21 +0200 From: Michel Talon <talon@lpthe.jussieu.fr> To: Jos Backus <jos@catnook.com> Cc: freebsd-ports@freebsd.org Subject: Re: UPDATING 20110730 Message-ID: <20110801172121.GA57098@lpthe.jussieu.fr> In-Reply-To: <CAETOPp1Mgrq8PbYQN1n_MjpnqxCmfkBvAUnXDgtDQKDf%2BqJ1Ng@mail.gmail.com> References: <20110801085135.GA45113@lpthe.jussieu.fr> <4E367999.8000906@FreeBSD.org> <201108011609.34885.talon@lpthe.jussieu.fr> <CAETOPp1Mgrq8PbYQN1n_MjpnqxCmfkBvAUnXDgtDQKDf%2BqJ1Ng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 01, 2011 at 09:39:05AM -0700, Jos Backus wrote: > On Aug 1, 2011 7:10 AM, "Michel Talon" <talon@lpthe.jussieu.fr> wrote: > [snip] > > This being said if an upgrade tool needs to compute (partially) the INDEX, > > most of the time is spent in running make -V <variables> in each port, > > because make has to read and interpret enormous files. I don't see any way > to > > cut on that, or one should need to develop a special purpose version of > make > > to evaluate these variables, perhaps which should keep persistent > > computations between ports (but this is dangerous). > > Or don't store lots of data in files in Makefile format. The make language > is a poor data storage format that doesn't allow access to that data from > other tools easily or efficiently. I'm struggling with a similar problem at > $WORK. > > Jos This is unfortunately impossible because the ports system is organized around a make logic and the relevant dependency variables are only obtained through running make on each ports Makefile *in the context* of the gigantic makefiles (bsd.port.mk, etc) which are included. -- Michel TALON
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110801172121.GA57098>