Quoting devzero2000 <pinto.elia@xxxxxxxxx>:
On Tue, Mar 3, 2009 at 4:41 PM, <rpm@xxxxxxxxxxxx> wrote:
I'm working on an rpm that creates a Linux repository on a server. I'm
calling it repo-1.0.0-1.i386.rpm. Basically I want to take all the rpms
from the distro DVD and install them in the web root, run createrepo on them
and a few other minor things and be happy.
Normally when building an rpm I would take all the files I need and package
them into the rpm and let rpm install them. Doing that with this rpm makes
the rpm huge between 2 & 3 Gig although it does seem to work. This rpm also
needs to be added to a custom distribution DVD so adding this rpm to the
custom DVD iso basically doubles it in size.
It seems more logical that since I already have the DVD media handy to make
an rpm with a post script that takes the rpms off the DVD and puts them in
the right spot, does the few minor tweaks and I'm good to go. This makes
for a very nice very small rpm. It works fine when testing the rpm on a
test bed. The script behaves predictably and mounts the DVD, grabs the
files and puts them in the correct locations. It's another story entirely
when the rpm is included in the system kickstart and installed when the
server is first created. None of the post script actually functions.
In fact any minor command that I run as part of a post script in an rpm
that is installed when the system is being built seems to fail.
I am pretty sure that you have an kickstart package ordering problem. This
fire the bug with the deps do by anaconda in installation.
Are sure do you have something like this in the beginning of your kickstart
?
%packages
@core
I checked and I DO have the @core group installing with the kickstart.
Where can I find more about package ordering?
Also, I'm not sure if this is pertinent or the venue for this or not
but I'm creating a new ISO image of the DVD. I'm adding the repo*.rpm
to the list of rpms already on the DVD and running createrepo which
takes quite a bit of time. Then I create a new ISO image and use it
to install. Is there a way of just adding a separate directory to the
ISO image and somehow telling anaconda about the directory? That way
I only need to do the createrepo command on the smaller directory. I
guess my question is, "How does anaconda know where to look for rpms?
BTW Its RHEL 5.3.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
