Hello, Am Dienstag, 8. November 2016, 15:59:28 CET schrieb Dominique Leuenberger / DimStar:
You have up-to-date indexes on Tumbleweed that work and don't require you to mess around every few days?
Well, that's something I'd really like to have ;-) I know that generating ARCHIVES.gz takes quite a while [1], which means generating it for each Tumbleweed snapshot would take too long (unless we find a way to improve the performance [2]). Maybe updating ARCHIVES.gz only once a month would be a solution that works for nearly all users without hammering the build infrastructure too much. Just put an ARCHIVES.README next to it to make it clear that it can be slightly outdated. I also agree with Carlos that we should keep pin in Leap. Leap comes with an ARCHIVES.gz, so pin is clearly useful there. BTW: one of my personal usecases is to find out which packages ship an AppArmor profile [3], so that I can review those profiles from time to time. Regards, Christian Boltz [1] IIRC, a while ago, someone wrote it takes a day. I don't know if the hardware performance or the number of packages increased faster since then ;-) [2] I'd guess that caching the rpm -qp --$other_options output in a file for each package could help a lot - cat'ing those files together is much cheaper than some thousend rpm -qp calls. [3] Thanks to Bernhard, I can now get the filelist for exactly this usecase online. That's nice for me ;-) but doesn't cover other things people might want to do with pin. -- Btw. in general my plan is: * Release AlphaN * Break everything;-) (I mean: put new stuff in that could be broken) * Stabilize again in time for our AlphaNplus (after two weeks) * Stabilize furthr for the next public Alpha [Andreas Jaeger in opensuse-factory] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org