[Pkg-scicomp-devel] Remove or move old packages in SVN?

[Daniel Leidert]

Am Montag, den 12.05.2008, 22:54 +0200 schrieb Ondrej Certik:
> On Mon, May 12, 2008 at 5:57 PM, Christophe Prud'homme <prudhomm at debian.org> wrote:
> > On Sun, May 11, 2008 at 3:06 AM, Daniel Leidert <daniel.leidert.spam at gmx.net> wrote:

[..]
> >>  - tags/{package1,package2,....}
> > I agree with that but I guess we have to customize svn-buildpackage
> > for the -svn-tag to work, no ?
> 
> 
> I suggest to use the default way of dealing with packages using
> svn-buildpackage, so that new people can easily learn it.
>
> I.e. doing things the same way as others, for example the Debian
> Python Modules Team, or any other team that uses svn.

If you don't set the tagsUrl value in the configuration files,
svn-buildpackage tries several possibilities itself. Unfortunately, it
will not detect

/tags/foobar/

from

/package/foobar/trunk/

But like mergeWithUpstream you can also set tagsUrl as a SVN property.

svn propset svn-bp:tagsUrl \
    svn+ssh://svn.debian.org/svn/pkg-scicomp/tags debian

IMO this is safe and can be done for every package. So no user (even
novice users) will need to customize his svn-bp installation or
configuration for tagging.

There are more possibilities (e.g. using a symlink), which have
disadvantages (e.g. a dead symlink, if one just downloads a package).

I'm just annoyed by these masses of useless stuff in tags/, which I
don't need to work with on a package. And for the QA work I recently
did, I also cannot check out just trunk/ per package easily. I would
have to do this manually for every package. I tried this, and it was a
mess (`for i in' loops and such stuff, just to update all trunk/
directories together).

However, there is currently a bug in svn-buildpackage (#480684), so I
wanted to delay the tags movement until this has been fixed anyway.

Regards, Daniel