From: Jeff Squyres; Wednesday, November 3, 2004 04:31 PM > > Not before SC / 4.0.
Agree to both. My original expectation was that the cache would be pre-computed and the correct cache select at install time. That process will now work even better, as the pre-computed cache will now be updated on an rpm-by-rpm basis with actual package info if some/all of the rpms were updated betweeen the time we pre-computed the cache and the time of the install. FWIW, this cache update actually now occurs when the server packages are installed in Step 3. It's pretty quick, about 3-6 seconds on vmware. > On Nov 3, 2004, at 12:21 PM, Benoit des Ligneris wrote: > > > I wonder if it is judicious and possible to distribute the already > > computed cache of update-rpm with the OSCAR tarball. > > > > We can simply generate such a cache for every distributed RPM and it > > will certainly speed things up. > > > > Also, this is very interesting for developpers as testing will be > > faster... -- David N. Lombard Rossmoor, Orange County, CA N 33 deg, 48', W 118 deg, 5' ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
