Re: just built garnome on Debian Woody...

[Nick Moffitt <nick zork net>]

begin  Mr. Denis A. Saveliev  quotation:
> - It would be very useful to have a full list of downloads that
> garnome perform, just to have possibility to download all packages
> somewhere and take it home to build, for people like me who don't
> have fast connection at home.

	Try making a garchive and hauling that home.

> - pay more attention to define the compiler version at the very
> beginning of compilation. Maybe it would be useful to do some global
> configuration pre-search just for compilers and libraries needed for
> the whole meta-desktop to build ? I faced the problem that I have to
> get new compiler and libraries somewhere in the middle of
> compilation process, because standard (for woody) gcc just couldn't
> compile it.

	The solution we use in the LNX-BBC (the original GAR tree) is
to build a full toolchain, including libc, binutils, etc.  We actually
treat everything as a cross-compile (i386-pc-linux-gnu to
i386-lnxbbc-linux-gnu), but that's because we're shithouse
crazy.

	But the goal of GARNOME is to test development releases of
GNOME in various environments.  Some of the predependencies can be
solved, but some things you just want to test and file a bug.  I think
the gcc version thing would be a WONTFIX, but you could always install
gcc-3.0 in woody and that'll work unless the packages in GARNOME
really REALLY need 3.2 (possible, but I'm still chilling with
GNOME2.2, so I'm kind of a heretic on here).

> - When the compilation stopped because of lack in ncurses-devel
> package (my fault, of course, but - ) it couldn't resume compiling
> after the package was installed, so I couldn't do anything but start
> compilation from zero point. Maybe you should do something with this
> in the distribution. All other missing headers didn't produce such a
> trouble, the compilation could be resumed after the needed package
> is installed.

	Do you mean that you had to restart the full build over, or
that you had to unpack your GAR tree afresh?  My guess is that the
worst case would be that you need to do a "make clean" in the
directory for the package that died, and start your build again.  GAR
manages cookies for dependencies and other build elements, to prevent
repetition.  Surely your restart just skimmed down the list of
packages until it hit the previously broken one, yes?

-- 
"Forget the damned motor car and build cities for lovers and friends."
	-- Louis Mumford

end