On Mon, Aug 17, 2009 at 03:37:35PM -0400, Daniel Richard G. wrote:
> As far as I'm aware, there isn't a good way to know. So the caveat is
> that if a cache has short-filename packages, then it can't handle
> multiple distributions, unless the packages somehow have the same
> checksums across the board. (Which is possible for locally-built .debs,
> I suppose.)
> 
> Existing caches have basically "thrown away" some of the relevant
> package information, which the new approach would save, so some
> additional work would be needed to get that information in for the
> existing packages. The proposed two-step fallback is less about "let's
> make existing caches able to handle multiple distros straightaway" and
> more about "let's not effectively clear out everyone's caches by no
> longer looking for packages under their old names" :-)

OK. 

I am concerned that there might be some users on low end systems with
poor bandwidth and/or disk space who might consider the traditional lack
of redundant downloads as a real feature. So, since a multi-distro cache
can't use short-filename packages, how about a configurable approach?
If we set the value of $new_filename to either the long (new) or short
(old) version dependent on a flag in %cfg. Long filenames could even be
the default for new installations. Existing users wouldn't notice
anything.

I actually have version 1.7 nearing completion. It contains goodies like
Range support, checking diskspace and cleaner (I hope!) handling of
requests and responses using objects. I think this might be something to
add in there.

Mark



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to