RE: [Oscar-devel] wizard startup time

[Jeremy Enos]

No... just as with no seeder cache, the cache should absolutely never get 
used w/o getting update called first.  Otherwise, we would be susceptible 
to any change the user made in the directory after the initial 
update.  updaterpm should be capable of *synchronizing* it's cache (adding 
or removing entries) efficiently, and thus making a seeder cache really 
useful.  Dave said on a call that it would be capable of this.

        Jeremy

At 10:08 AM 3/1/2004, Jason Brechin wrote:
What happens if there's information for a package in the cache, but the
RPM doesn't actually exist?  That's a big problem if we decide to
distribute a cache.
Jason

On Fri, 2004-02-27 at 15:41, Lombard, David N wrote:
> I had originally assumed the cache would be generated during the *build*
> of the oscar packages for each supported distribution.  If additional
> RPMs are present, e.g., via an update of the original CD, then the
> --cache=update would be quite quick.
>
> Also, don't forget, on a real system, even my laptop, it's only a few
> minutes to build the complete cache from scratch.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel