[Archiver-dev] UpLib and archiving

[Barry Warsaw]

Hi Bill, thanks for the response.  Let me address one issue first.

On Oct 19, 2010, at 12:38 PM, Bill Janssen wrote:

>Why is a VCS necessary for that?  I usually just visit the tarball with
>Emacs :-).

Good thing you didn't say "vim" :)

>I'm not set up for that right now (and not sure I want to be), so I
>don't think that will happen in the near future.  I still like using CVS
>(I know, I know, but I like the annotations on individual files) with
>point-release tarballs.  I suppose each point-release tarball could be
>used to update a Mercurial VCS, right?  Clearly needs more discussion.
>
>But the source is up there -- feel free to unpack it into something
>you're more comfortable with to look at it.

If you're more comfortable with CVS, that's totally cool.  One advantage of
making the CVS (read-only) publicly available is that we can set up imports
into other vcs's.  For example, we could point Launchpad at your CVS
repository and import the code into Bazaar.  I'll bet bitbucket can do
something similar for Mercurial.

The advantage of that then is that folks can use the vcs they are comfortable
with but have access to all the revision history, more easily generate patches
that won't conflict when you try to merge them, and more easily follow your
development.

The alternative is to manually import the tarballs into the vcs, and hope
there are no conflicts, file moves, or other changes that are near impossible
to make work manually.  Another problem of course is that everyone will have
to do that manually for the vcs of their choice.  Or if we don't use a vcs and
just hack the tarball, it will be pretty difficult to get you reliable patches
that you can review and integrate.  Not fun!

If you made your CVS repo (read-only) available, I'd create a project on
Launchpad for uplib, link it to your repo and bug tracker, and work to get the
package into Debian and Ubuntu.

Just something to think about. :)

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/archiver-dev/attachments/20101020/2e0a6e2f/attachment.pgp>