Re: Depositing source archive at Alioth.
tisdag den 7 december 2010 klockan 09:51 skrev Russ Allbery detta:
> Mats Erik Andersson <mats.andersson@gisladisker.se> writes:
>
> > I am working on an ITP regarding rgPaint and I maintain, ever since
> > starting, the corresponding directory "debian/" at Alioth/deb-maint.
>
> > Which is the correct location to deposit the corresponding upstream
> > source archive? The builds on my systems use "tarballs/", but in
> > conjuction with collaborative translation work for additional docu-
> > mentation, the present matter comes to my mind.
>
> There is no particularly good way of handling this with Subversion. With
> Git, you can just use pristine-tar, which is a far superior way of storing
> tarballs than checking the compressed tar file into a version control
> repository, but that isn't available for Subversion.
My initial phrasing is not clear enough, but I am asking since I believe
to recall having seen a suggestion
svn-ssh://svn.debian.org/svn/collab-maint/deb-maint/<package>/<something>/current
and a similar path for numbered versions of the original tar-ball.
Once done, the setting of the key word "svn-bp:origUrl" to the path
of storage would do the work for use with svn-buildpackage.
>
> Some people don't check the tarball into anything and just assume that
> anyone building the package will either get the current tarball from the
> Debian archive or generate a new one if there's a new upstream. Others
It is exactly here that I get insecure. For the time being, i.e., as long
the ITP is going on, there is no "rgbpaint_0.8.7.orig.tar.bz2" available
anywhere in a Debian repository, so I would like to find a natural location
for depositing the archive. Ideally it should not be handled by any VCS,
just be considered as a fixed artifact, until I manage to see the package
progress into NEW. (I have a volunteering sponsor already.)
> create some separate module in the Subversion repository and check the
> tarballs into that. Others organize the layout inside the repository so
> that each package has the tarball at the top level of the package's module
> in the repository and the unpacked files in a directory below that, which
> means that debuild will work by default.
>
> So, basically, you have to decide. For the NVIDIA packages, we have an
> nvidia-tarballs module in Subversion and check all the tarballs into that,
That is the solution also of the Games Team, so there I can deposit the
tarball from the upstream I manage.
Thanks for your illuminating explanation.
Best regards
Mats E Andersson
Reply to: