Re: [ANNOUNCE] GARNOME 2.17.91 -- "go go gadget garnome"

[Peter <sw98234 hotmail com>]

On Fri, 16 Feb 2007 11:55:38 +0000, Yiannis Mavroukakis wrote:

> Hmm perhaps there is another way :) 
> 
> Say you have the garnome 2.17.90 tree fully compiled and installed and
> you haven't cleaned it.
> 
> You download 2.17.91, unpack it and then run a fictional "make upgrade".
> Before that, in gar.conf.mk you have a variable that points to the
> previous tree. make upgrade starts and for argument's sake looks at gdm.
> For garnome 2.17.91 GDM version is 2.17.7 and for 2.17.90 it's 2.17.6. 
> Since GDM has dependencies , gar follows those checking for versions as
> it goes and flagging which ones need to be uninstalled and
> updated...does this sound feasible?
> 
> Y

No. Garnome is a monolithic, self-contained build system.. What you're
suggesting IS logical, but would take an extraordinary amount of work.
Mostly I am cynical because of dependencies. The best way to save time is
to prevent compilation of modules that may reside on your host system.
This will protect against duplicate copies of programs being compiled.

This is something I have been working on extensively but is not supported
at all by the garnome devs.

This will not save time when remaking the desktop or office, but there's
no reason you could not try and say make install for the office changing
the gar path. Your mileage may vary. You would have to remove the install
cookie files. 


> --
Peter