lets talk about dependancies again...
Greg Kurtzer <[email protected]> Thu, 3 Oct 2002 20:02:38 -0700
| Newsgroups | gmane.linux.redhat.rpm.grab |
|---|---|
| Message-ID | <[email protected]> |
OK, RedHat8 is using RPM41, so I really should get on the ball here. I have several options moving forward. I already got GRAB to deal with RPM41, but it is not very quick (the older version of RPM seemed to do the remote provides gathering MUCHMUCH quicker). I will need to do something about this. Has anyone played with the new version of RPM enough to know how to create several RPM datbases, and merge them into one? This way I can have the GRAB friendly repository build an RPM database for each repository directory (via a tarball), and bring them local and merge them. Then I can run some tools against that database to obtain requires info. I am still throwing around ideas, so speak up if you have one... I would like to use some of the RPM internals to do much of this, and would rather not reinvent the system (as I have already done in some senses). As far as the order of operations goes with GRAB dependency checking, here is what I propose. If it is a GRAB friendly repository, we will do the above. If it is not a GRAB friendly rep, then GRAB will do it the old fashion way which is to download the package not knowing if the deps are met, then parse the output of an 'rpm --test' for problems, and try to resolve those problems before calling the install. This will be a large code change, and will start the new devel tree (probably 1.1). Any ideas on the methodology? Thoughts? -- Greg Kurtzer [email protected] http://www.runlevelzero.net LINUX,... The choice of a GNU generation! :wq