Re: [gentoo-dev] sys-build

[<drobbins@gentoo.org>]

On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:

> Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
> minimum required stuff, we can even place gcc and binutils in separate TARGET
> dependent packages, so it should be possible to make one cd that gives you
> the ability to build for all our intel targets.

OK, so we have two install CD's:

1. the standard packages CD (for people who want a quick install)

	/images/sys.tbz2
	/packages/<all your .tbz2 packages here>

2. the autobuild CD (for people who want to build everything from scratch)
	On this CD, the directory structure looks something like this:

	/portage
	#profiles contains lists of packages to install for various types of
	#systems, such as "desktop", "server", "router", etc.
	/portage/profiles
	/portage/distfiles
	
	# the i486, i586 and i686 build packages contain gcc and binutils
	# compiled for their respective targets... question, is this necessary
	# since you can access these sub-architectures with compile-time switches.
	# this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or
	# are there more extensive changes besides this?  How about binutils?
	# If there are no differences in generated code, we can have a single
	# build.tbz2 instead of three.

	/gentoo/i486/build.tbz2
	/gentoo/i586/build.tbz2
	/gentoo/i686/build.tbz2

> Well there is no base-system that needs to be rebuild. Instead the
> corresponding non statically linked packages get build and merged over or can
> be unmerged if not required after the build.

Again, why are these static?  I'm guessing so that you don't need to include
certain libraries?  Wouldn't build.tbz2 be smaller with dynamic linking?

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.