Hi,
When building an installation CD with pungi, the packages needed for Anaconda need to also be present in the 'repository'. (this is probably generic for building an Anaconda installer?)
Is there a way to differentiate between RPMs that are needed for Anaconda and the RPMs that should end up as 'installable' on the disc?.
Example: baseurl_anaconda=http://...FC6.url.../ baseurl=http://..MyOwn.url.../
Here 'baseurl_anaconda' is some place that Anaconda can get RPMs from (the PACKAGES from Anaconda upd-instroot) and 'base_url' is the place for 'installable' RPMs.
Any thoughts?
Best regards,
Jeroen Janssen
Hi,
Dnia czwartek, 23 listopada 2006 16:40, Jeroen Janssen napisał:
Hi,
When building an installation CD with pungi, the packages needed for Anaconda need to also be present in the 'repository'. (this is probably generic for building an Anaconda installer?)
Last time I have used it (anaconda scripts) - there was a separation. I've had two separate directories with RPMS (one for installer, the other for the distro). Because of that feature I've been able to have different kernel versions in distro and installer.
On Thursday 23 November 2006 10:40, Jeroen Janssen wrote:
Any thoughts?
I've talked with the anaconda folks, and they want to change how some of the stage files are created, so that you don't need a lot of the crud at tree build time, just enough to poke at the kernel and create the boot images. The rest of the stuff (languages, gui files, etc..) would be created when the anaconda-runtime rpm is built in the buildsystem. This would reduce the number of 'needed for building the tree' packages that wouldn't be _in_ the tree already. Because of this I haven't put any logic in Pungi to separate the two package sets.
buildsys@lists.fedoraproject.org
-
Jarosław Górny -
Jeroen Janssen -
Jesse Keating