Re: Subversion move

[Frank Küster <frank@debian.org>]

Hi all,

the subversion repository has been created on Alioth.


I've been thinking about how to populate it, and would appreciate your
comments:

- As for the repository structure, I'd suggest to use the package names
  as the toplevel dirs, as in our old CVS repository, and otherwise the
  default structure that svn-buildpackage/svn-inject will use. Any
  objections? 

- svn-buildpackage offers the option to only import the files actually
  changed (i.e. mainly the debian directory), and keep the rest of the
  orig.tar.gz out of version control.  On a first glance, this looks
  nice for tetex (especially -base), because it would safe lots of disk
  space, and possible transfer time.

  On the other hand, we have now a nicely working system to
  automatically generate and change patches, which relies on the
  existence of the complete source tree besides the debian directory.  I
  tried whether it is possible to have both - a checked out working copy
  copied into the upstream source tree which was not under version
  control, but it doesn't work well: There is at least one file that we
  actually add in the diff.gz (doc/generic/pstricks/README.pst-oscii),
  and therefore we cannot simply set the svn:ignore property for the
  whole doc subhierarchy; however when doing this for the other files in
  there, svn-buildpackage fails.

  Therefore it seems that using this MergeUpstream option forces one to
  really keep the upstream sources elswhere, and I don't think this
  would be good for us.  What do you think - how important is disk space
  and bandwidth for you - remember that you can always check out only
  the debian dir, or check out everything once and update only the
  debian dir.  And package building worked fine for me for ages with

  cp -a tetex-base-3.0 compile-area/
  find compile-area/tetex-base-3.0 -name "CVS" | xargs rm -r

  so it will also work with s/CVS/.svn/.


These are the questions that I noticed so far, please feel free to add
more. 


By the way, I found that the password for the shell login on
alioth/cvs.debian.org is the same as for the alioth website.  Is there a
way to disable password login on a per-user basis after RSA
authentication is set up?

Regards, Frank
-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer