Re: updates.img since anaconda-11.4.0.36-1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeremy Katz wrote:
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.

with anaconda, you never stop learning :)
thx for the correction.


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

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

--
Joel Andres Granados
Red Hat / Brno, Czech Republic

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux