On 2 February 2016 at 19:03, holger krekel hol...@merlinux.eu wrote:
I think there is no way currently to remove old versions besides going through the files directly. A plugin to devpi-server using some internals could implement that though.
I think more precise cache handling didn't come up so far because most people including me don't seem to worry too much disk space usage. Do you have an idea how you'd like to remove cached packages UI-wise? hand-selecting them? Removing all but newest versions for each package?
I guess one could try to make "devpi remove" work for mirror indexes -- it accepts version specs like pytest<2.6 etc. but currently only works on private indices.
I wasn't really thinking it was something I'd need for anything specific, I'd just sort of imagined there might be some sort of "manage the cache" command I'd missed. I was thinking in terms of something like a "devpi cache" command with subcommands for various things
devpi cache list -- lists what's in the cache devpi cache remove PACKAGE [--outdated] -- remove all files for PACKAGE (or all but the latest)
I was thinking that such a command would also include some sort of "devpi cache add" subcommand to populate the cache (hence my original question).
But this isn't a case of "I would need these things", more that I'd assumed there was some form of cache management that I'd missed (and if so, this is how it'd look).
I'm OK with just doing "pip download" via the cache to pre-seed it. If I want a more "controlled" mirror I'm probably better off just doing "pip download" direct to get the files locally, and using --find-links to let pip find them. Something like devpi is probably more complex than I need if I'm going to do things that manually, anyway.