Hi, On Mon, 4 Jun 2007, Duncan Mac-Vicar Prett wrote:
On Sunday 03 June 2007 20:03:07 Duncan Mac-Vicar wrote:
It has to remain. This attribute will be used to associate the plain text "repo infos" in /etc to the cached data in the binary cache. Of course I could associate using the sha on the index and update it all the time, but that would prevent you from refreshing the raw metadata from building the binary cache in two steps.
I switched to using the alias for now.
Now I get it, you were talking about the md5 sum of the .repo file,
Yep. Using the content itself (well, mostly so) as unique identifier :-)
Yes, as you said, the cache survives through .repo file changes, still it is not a bad idea, you can just force the user to rebuild the cache if the .repo changes and cleanup the orphan caches.
If that indeed doesn't happen that often, then using the MD5 of the .repo seems like the most robust solution. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org