Re: Order to compile

begin  Jonas  quotation:
> Exists some order to compile the different packages that there are
> in each category? Or simply it is guided by the dependencies of each
> package. If it is thus, why category and package begins?

	Typically we create packages in meta/ that we consider to be
the "first" package, or the "top" of the tree of dependencies.  The
idea was to make a package that just depends on all the installed
software in your OS image and then prepares it for distribution or
some other purpose.

	So meta/lnx-bbc is theoretically the package that depends on
all of the BBC's software, and it builds the CD-ROM image.  In
actuality, we've broken meta/lnx-bbc down into a number of
sub-packages to make our lives easier (one important one is
meta/singularity).

	
	So it is true that if you simply typed "make install" from the
top-level directory, you would just install software alphabetically
by category.  The goal of GAR is that you can do that and it will
cause no harm, but we've done so many complicated world-separation
techniques to keep our various filesystems straight in the LNX-BBC
that our tree may not work well this way.

	However, the GARNOME project has done away with the notion of
the metapackage, and you actually do install the whole thing by just
running "make install" in the top directory.

-- 
The insipid neologism "blog" appears to mean little more      Nick Moffitt
than a Web site that *actually* gets updated, as opposed     [email protected]
to one that *promises* to be updated REAL SOON NOW and
includes an animation of a MEN AT WORK sign.