I just edit the comps.xml to cut packages from group [core] or [base] and so on - Original Message ----- From: Masoud Sharbiani <masouds@xxxxxxxxx> Date: 20 Feb 2003 15:39:40 -0500 To: joseph.r.bezouska@xxxxxxxxxxxxx Subject: Re: RPM Installation Ordering > Try to generate a graph of rpms you intend to install. Run rpm -qp > <yourpackage> --requires and rpm -qp <yourpackage> --provides to > generate a directed graph. > Now, install can be done from any 'root' node (nodes that don't require > anything.) remember that requirements might not be explicit. for > example, most programs would have a dependency to /lib/libc.so.6 even if > they don't have explicit 'requires: glibc' in their .spec file while > build. > clear enough? :-) > Masoud > On Thu, 2003-02-20 at 15:27, joseph.r.bezouska@xxxxxxxxxxxxx wrote: > > mattdm@xxxxxxxxxx wrote: > > >On Thu, Feb 20, 2003 at 11:46:12AM -0600, joseph.r.bezouska@xxxxxxxxxxxxx > > wrote: > > >> >> 1. glibc-common > > >> >> 2. hwdata > > >> >> 3. redhat-menus > > >> >> 4. setup > > >> >> 5. filesystem > > >> >> 6. basesystem > > >> Thanks -- long term, a custom CD is likely the goal. > > >> Short term, it's curiousity about what is "sepcial" > > >> about these 3. > > > > > >Simple -- basesystem requires setup and filesystem, so those go before > > that. > > >glibc-common, hwdata, and redhat-menus don't require anything at all, so > > >there's no particular reason to order them anywhere special, so first is > > as > > >good as any. > > > > > > > > >> Why these and not, just for sake of example, > > >> say bdflush? > > > > > >bdflush requires glibc. > > > > > > > > >-- > > >Matthew Miller mattdm@xxxxxxxxxx <http://www.mattdm.org/> > > >Boston University Linux ------> <http://linux.bu.edu/> > > > > > > > > > > thanks very much -- this makes good sense. > > some simple tests bore it out: > > > > added the following carefully selected RPMs to > > the 8.0 Base/Core install, making sure they were > > on CD #1: > > > > - modutils-devel (req's nothing; nothing in Base whatreq's) > > - gnome-vfs2 (req's the following) > > - gnome-mime-data (req's nothing; above whatreq's) > > > > [ BTW, great thanks to anaconda-runtime's pkgorder > > utility for finding this last one -- seems the > > only one like that on CD #1 besides glibc-common, > > hwdata, and redhat-menus -- better than churning > > manually thru comps ] > > > > found: > > 1. modutils-devel installs (nearly) last > > > > 2. gnome-mime-data floats up and installs (in alpha > > order) first right along with the original RPMs > > of question: > > > > 1. glibc-common > > 2. gnome-mime-data > > 3. hwdata > > 4. redhat-menus > > 5. setup > > 6. filesystem > > 7. basesystem > > > > > > so, stuff with no req's and with no whatreq's float > > down to the bottom (naturally), while stuff with no > > req's but with whatreq's float way up to top (even > > before basesystem, which I did not expect and was > > tripping me up). > > > > good that Red Hat Linux observes Occam's Razor, > > though. > > > > thanks again. > > > > > > > > > > > > > > > > > > This message is for the designated recipient only and may contain > > privileged, proprietary, or otherwise private information. If you have > > received it in error, please notify the sender immediately and delete the > > original. Any other use of the email by you is prohibited. > > > > > > > > _______________________________________________ > > Anaconda-devel-list mailing list > > Anaconda-devel-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/anaconda-devel-list -- ______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze
