[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: updates.img since anaconda-11.4.0.36-1
- From: Jeremy Katz <katzj redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: updates.img since anaconda-11.4.0.36-1
- Date: Wed, 20 Feb 2008 09:44:52 -0500
On Wed, 2008-02-20 at 09:33 +0100, Joel Andres Granados wrote:
> isys.c and the likes go into the stage2.img (squashfs) To get a new
> isys.c into the installation you would have to rebuild anaconda, put
> isys.so into new stage2.img, put stage2.img image in tree, install.
> FYI, updates.img is for .py file, you can also put stuff there that
> you want to have at install time (a text file or whatever).
This is partially true. You can also build isys.c into the _isys.so
shared module that's used by python and also stick it into an
updates.img. PYTHONPATH impacts loading of "native" modules as well as
byte-compiled ones.
Other things that you can stick into updates.img are updated shared
libraries as we set LD_LIBRARY_PATH appropriately also.
> You can also wait until rawhide builds successfully. There is a build
> every night AFAIK, the problem is that its not always sane.
The build uses the latest built anaconda, though, which isn't always the
latest bits from git.
Jeremy
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]