On Fri, 5 Aug 2005, Bob Proulx wrote:
3kr1ltp02@xxxxxxxxxxxxxx wrote:
What I'm trying to do is setup a build enviroment for my users who depend
on certain releases of compiler & libraries that came with redhat9. My
approach has been to install a box from media that works an a build host
with the smallest number of packages, and then use that list
(/root/install.log) to 'rpm -Uvh --root /some/new/rootDir someRpm.rpm' over
the entire list on a non redhat9 box. Seems reasonable. The list is about
500 packages.
yes we do this all the time too.
...
So my questions are these:
1. Is there a better approach? Maybe this is a common task.
scripting is your friend
I have been snapshot'ing live working systems into build chroot's.
This works but I have been wanting to move to a better system which
uses the package manager such as you are suggesting. So while this is
not an uncommon task I don't have great processes to suggest to you
for managing it.
yes, after making a root for a project, we back it up as a tar ball too.
This allows us to roll back to start very quickly.
...
http://hackers.progeny.com/~sam/rpmstrap/
but, this tool looks nice, if you want magic, on its supported versions
I recommend a roll your own script, like the one down below for creating a
centos 3 circa last month. notice the "pushd /var/spool/up2date" to change
to the local cache dir for the rpms to create the root. On the list there
is a break. It signifies the rpms needed to get bash/rpm running, the next
group is to get up2date/(yum?) running.
I like our engineers using a script like this, since we can repeat it any
day, any month, any machine. Just get the script out of cvs, grab the rpms
SPECIFIED, and run.
see part 2
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Partner & Sr. Manager 7 West 24th Street #100 -
- +1 (443) 921-0381 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
