> > it would be great if there was an option to not delete obsoleted > > packages when a newer version is installed, similar to mini-dinstall's > > keep_old option. this would make it easier to maintain an archive with > > all the historical versions of a package(or packages). > > That is quite complicated to implement. The current database structure > assumes there is at most one version of each package in each target > (as I internally call each distribution-component-architecture-type > unit, i.e. each Packages or Soruces files). I doubt this is easily > implementable.
oh well. :( > It's on my very-far-goals list as this would also be needed to keep > all sources in case of diverging versions amoung different > architectures, though I fear it is realy far away. such is the way of things. > The only thing near this is the --keepunreferencedfiles option, which > globally does not delete or forget any old files, but keeps them > unreferenced (but remembering their names and md5sums) in the pool/ hirachy. > If there is the need, I could look into adding a global config to > make such a option switchable by some to be implemented global config. a global option would be good, and a per-distribution option would be even better. sounds like it would be good enough for my needs, at any rate. thanks for giving it some thought. live well, vagrant
signature.asc
Description: Digital signature
