|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Mike A. Harris (mharris_at_redhat.com)
Date: Wed Nov 20 2002 - 04:32:39 CST
On Mon, 18 Nov 2002, Ted Goodridge wrote:
>Date: Mon, 18 Nov 2002 11:53:59 -0600
>From: Ted Goodridge <tedgoodridgejr
acm.org>
>To: axp-listredhat.com
>Content-Type: text/plain;
> charset="us-ascii"
>List-Id: Linux and Red Hat on Alpha processors <axp-list.redhat.com>
>Subject: Building Redhat from source/scratch
>
>For reasons such as bad linking etc, and the fact that I want to help out with
>redhat as much as I can, how do I build the distribution from scratch?
>
>I have all the rawhide SRPMS, and want to do it inside a chroot enviornment.
>I thought I could report any errors I found to bugzila. Is there
>documentation on how to do this? I would love to be able to read a document
>rather than bugging you guys.
There are several different ways that you could go about this,
each of which would provide useful information.
Red Hat rebuilds the entire distribution every single night on
all architectures, the resulting packages of which get tested for
various issues. We continue to add automated tests to catch more
and more errors.
If you're interested in helping do automated tests also, you can
use the rpm commandline options --initdb and --dbpath to specify
a new database location inside a chroot area, and --dbpath and
--root in order to install RPMs into the chroot area, without
affecting your main system or its RPM database.
You can just install all packages into the chroot, and then place
all src.rpm's into the chroot as well. Warning: do not install
or build multiple RPMs at the same time using the default RPM
config. Any 2 RPM packages can overwrite each others files in
the SOURCES dir if they both have a file of the same name. Best
to just do them one at a time, saving the results. You can save
the build logs from RPM as well, and then examine them either by
hand afterward, or via automated perl scripts or somesuch,
looking for errors, warnings and other potential problems.
There is a tonne of R&D in this area that one could do to help
find and fix problems before they become problems. If only there
were more hours in a day. ;o)
TTYL
-- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer XFree86 maintainer Red Hat Inc._______________________________________________ Axp-list mailing list Axp-list
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]