Jesse Keating wrote:
On Tue, 16 Oct 2007 14:51:10 +0200
Joel Andres Granados <[EMAIL PROTECTED]> wrote:

It been a long time since I had a hard look at pungi.  I do
know that it went from config files to using kickstart. Maybe you can use the %post functionality of kickstart, not sure :(.

what version are you using? try using the latest version. http://hosted.fedoraproject.org/projects/pungi

The %post part of a kickstart file is not yet processed by pungi.  I
haven't decided if or how it would be used.

Also there has been a slight regression in configurability in pungi
with the move to using kickstart files.  You can no longer override
what "release note" files to lay onto the install tree.  This was the
method before to use to get files out of packages and place them on the
tree/media.  A file such as a kickstart file.  Right now unfortunately
you have to edit the source code itself, in pypungi/config.py.  You can
add another file regular expression to match your kickstart file, and
list another package to the packages to look in for those files that
has your kickstart file in it.



------------------------------------------------------------------------

--
Fedora-buildsys-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

I think you can also add the file to the resulting iso image.
it should be easier than changing the code (IMO)
1. you have to mount the iso image somewhere `mount -o loop /path/to/isoimage 
/mount/dir`
2. cp -rf /mount/dir /other/temp/dir
3. cp kickstart.cfg /other/temp/dir
4. umount /mount/dir
5. mkisofs ...
6. put iso on cd

I'm not really sure how the mkisofs command goes.  but you can always look at 
the pungi
code and see what is done there :)

Be sure that the copy takes two hidden files that are at the root.

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

--
Fedora-buildsys-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Reply via email to