On Fri, Feb 10, 2012 at 01:55:54PM -0500, Konstantin Ryabitsev wrote:
> I have a few comments off the top of my head:
>
> 1. "kup rm" will need to be modified, as it currently only allows
> deleting things that have a matching signature. The alternative
> is for UNPACK to create a foo.tar.manifest file that will be
> consulted upon "kup rm" to clean up any unpacked contents upon
> the deletion of the source archive. Note, that there are many,
> many gotchas with this solution -- e.g. .manifest should
> probably contain checksums, too, as there are bound to be
> conditions when two tarballs reference the same files, and you
> want to make sure that you delete files matching the contents of
> the old tarball, not the newer one, etc.
For this particular use case, I don't know if that would be necessary.
According to Junio, previously:
The k.org site kept these files under /pub/software/scm/git/docs/. The
in-development "master" version of pages were placed directly
underneath that directory, and the documentation pages for older
versions were kept in vX.Y.Z subdirectory of that directory.
If we tweak that slightly to "all versions are kept in vX.Y.Z
subdirectory, and the root version is simply a symlink or redirect to
the latest vX.Y.Z", then there is no deletion required. The pusher is
always adding new versions, and updating a link[1].
But even if it would be sufficient for this use case, kup developers
may not want such a half-implemented scheme in their protocol.
-Peff
[1] There is a slight complication that the subdirectories live _inside_
of the root directory, so it is not implementable with a single
symlink. You could get around that with a few clever http redirects.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html