Mathieu Bridon (bochecha@xxxxxxxxxxxxxxxxx) said: > On Tuesday, April 09, 2013 11:52 PM, Bill Nottingham wrote: > >If you wanted to keep more versions on the mirrors, you have the following > >options: > > > >1) Have mash create everything, and then run a script that prunes versions > >older than X, and re-runs createrepo. > [... snip ...] > >2) Have mash try and implement a date-based expiry itself from what it > >requests from koji. > [... snip ...] > >3) Have mash sort through the packages retrieved by koji, and pull some > >subset less than 'all' (the last 2/3/4 versions). > > > >This is probably doable - it requires requesting all tagged packages from > >koji and then doing some postprocessing on the list before you download > >them. It's merely a matter of code. > > It seems to me that all of these solutions focus on making mash do > more stuff, without ever changing Koji. It's the (somewhat) more agile component in that it can be changed with less downstream dependencies, fewer worries about deployment on infrastructure, etc. > But couldn't the Koji API grow a new parameter, which would be used > for specifying how many versions of each package to get at most? It certainly could. However, Koji's concept of 'newer' is (IIRC) entirely tied to build time/tag time in the repo, not NVR. So it may not be what we want. Bill -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
