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

Ondrej Certik ondrej at certik.cz
Mon May 12 20:54:30 UTC 2008


On Mon, May 12, 2008 at 5:57 PM, Christophe Prud'homme
<prudhomm at debian.org> wrote:
> Daniel,
>
> thanks for your _very_ helpful work and your suggestions below !
>
> On Sun, May 11, 2008 at 3:06 AM, Daniel Leidert
> <daniel.leidert.spam at gmx.net> wrote:
>> Hi,
>>
>>  Some packages in the SVN are not maintained anymore or are obsoleted.
>>  Two examples are gnudatalangauge (maintained outside) and ufsparse.
> ufsparse is indeed obsolete, should be removed
> if gnudatalanguage is not maintained, let's remove it
>
>>
>>  Could these be moved into an own directory (e.g. oldpkgs or oldlibs or
>>  similar) or be removed from the SVN? I just would like to have a better
>>  organizing of these 2.5GB repository. It would make it easier to check,
>>  which packages really need maintenance. I normally would suggest a
>>  top-level structure of
> I never realized it was that bad because I always retrieved package by
> package and never the full repo.
> now with your email I realize that some reorganisation is indeed needed !
>
>>  - old (only stable/oldstable)
>>  - packages (in Debian)
>>  - wnpp (not yet in Debian/ITP)
> agreed, good idea
>
>>  and maybe (see my other mail some days ago)
> I saw it on debian-science but didn't have time to  answer
>
>>  - 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.

Ondrej



More information about the Pkg-scicomp-devel mailing list