Re: Can pungi put packages in the iso that are not installed?
On Dec 23, 2008, at 12:41 AM, Jesse Keating wrote: On Mon, 2008-12-22 at 22:29 -0600, Joe Nall wrote: Can pungi put packages/groups in the iso that are not installed? Context: I'm building spin using pungi that includes packages that get installed in a second pass in a manner similar to firstboot. The packages require a number of services to be running to properly configure themselves and can't be grouped in the initial install. I want to include the packages in the repo, but not install them until the system has more services running. Sure! Just make sure they are in the %packages section of your pungi kickstart file and pungi will make sure they're on the install tree/media. Whether or not the user can select them during the initial install is of no concern of Pungi's. Sorry, I wasn't clear. Not an interactive install. joe -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
2008/12/23 Jesse Keating jkeat...@redhat.com: On Tue, 2008-12-23 at 08:01 -0600, Joe Nall wrote: Sorry, I wasn't clear. Not an interactive install. Doesn't matter. Put the packages in the ks file you feed pungi and they'll wind up in the compose, regardless if they get used later. Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? -Yaakov -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
On Tue, Dec 23, 2008 at 2:53 PM, Yaakov Nemoy loupgaroubl...@gmail.com wrote: Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? The ks file that you compose from and the one that you install from aren't the same thing. Not sure what the question is. -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
On Tue, 2008-12-23 at 14:53 -0500, Yaakov Nemoy wrote: 2008/12/23 Jesse Keating jkeat...@redhat.com: On Tue, 2008-12-23 at 08:01 -0600, Joe Nall wrote: Sorry, I wasn't clear. Not an interactive install. Doesn't matter. Put the packages in the ks file you feed pungi and they'll wind up in the compose, regardless if they get used later. Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? There is no requirement that the ks file you use to compose is the same ks file you use to install. In fact, them being so is somewhat silly, as if you have a local mirror, just do your installs over the network, instead of doing a compose and then installing from media. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating signature.asc Description: This is a digitally signed message part -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
On Dec 23, 2008, at 1:55 PM, Jon Stanley wrote: On Tue, Dec 23, 2008 at 2:53 PM, Yaakov Nemoy loupgaroubl...@gmail.com wrote: Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? The ks file that you compose from and the one that you install from aren't the same thing. Not sure what the question is. I was trying to avoid maintaining 2 ks files. I solved the problem by using sed to create an install ks from the pungi ks. joe -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
On Dec 23, 2008, at 4:31 PM, Yaakov Nemoy wrote: 2008/12/23 Jesse Keating jkeat...@redhat.com: On Tue, 2008-12-23 at 14:53 -0500, Yaakov Nemoy wrote: 2008/12/23 Jesse Keating jkeat...@redhat.com: On Tue, 2008-12-23 at 08:01 -0600, Joe Nall wrote: Sorry, I wasn't clear. Not an interactive install. Doesn't matter. Put the packages in the ks file you feed pungi and they'll wind up in the compose, regardless if they get used later. Would this require a second ks file that omits the package name, for the automated install, so that it will be on the media, but not actually installed by default? There is no requirement that the ks file you use to compose is the same ks file you use to install. In fact, them being so is somewhat silly, as if you have a local mirror, just do your installs over the network, instead of doing a compose and then installing from media. I got the impression that Joe Nall was trying to use the same ks file. Hence i asked, so we could all be clear on the details. :) Old school testers like DVDs :) joe -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
Re: Can pungi put packages in the iso that are not installed?
On Dec 23, 2008, at 3:50 PM, Jesse Keating wrote: On Tue, 2008-12-23 at 15:22 -0600, Joe Nall wrote: I was trying to avoid maintaining 2 ks files. I solved the problem by using sed to create an install ks from the pungi ks. Just curious, can I ask what output of pungi you're using and how you're doing the install? I have a package group @myapp-all that I want in the iso repo. I do not want the packages in this group prompted for or installed by anaconda. @myapp-all get installed after the first boot when some needed services are available (selinux-policy-mls and mcstransd). joe #!/bin/bash VERSION=`svnversion -n` NAME=MyApp BUILD=/var/tmp/pungi OS=$BUILD/$VERSION/`uname -i`/os/ ARGS=--destdir=$BUILD --bugurl=http://www.myapp.org/ --nosplitmedia -- nosource --name=$NAME --ver=$VERSION --force rm -rf $BUILD mkdir -p $BUILD pungi -c myapp.ks $ARGS -GCB # Customize boot menu and add remove @myapp-\* from first install cp myapp-install myapp-install.repo myapp.ks isolinux.cfg.patch $OS sed -e 's/^...@myapp-/#...@myapp-/' myapp.ks $OS/myapp.ks (cd $OS/isolinux sudo patch ../isolinux.cfg.patch) rm $OS/isolinux.cfg.patch pungi -c myapp.ks $ARGS --force -I -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
