I've just committed camlidl package under the "umbrella". I suggest you
to look at it as an example on how I intend to use the svn repository.
Suggestions are really welcome.
----------- SVN configuration -----------
Create a ~/.subversion/servers file as described by Remi, this is mine:
<<<< BEGIN >>>>
[groups]
pkg-ocaml-maint = pkg-ocaml-maint.alioth.debian.org
[pkg-ocaml-maint]
svn-tunnel = ssh zack@pkg-ocaml-maint
<<<< END >>>>
The base URL for the SVN repository is:
svn+ssh://pkg-ocaml-maint.alioth.debian.org/svn/pkg-ocaml-maint
----------- SVN repository layout -----------
This is the current layout of the repository:
/
/branches (empty)
/trunk
/trunk/packages
/trunk/packages/camlidl
/trunk/packages/camlidl/camlidl_1.04.orig.tar.gz
/trunk/packages/camlidl/debian/....
A directory for each packages (same name as the debian _source_ package)
containing an unpackage debian directory and the latest upstream tarball
with the standard debian convention .orig.tar.gz
----------- Package checkout and building -----------
Checkout the package:
$ svn co svn+ssh://pkg-ocaml-maint.alioth.debian.org/svn/pkg-ocaml-maint/trunk/packages/camlidl
Then, to work with the package, I suggest this approach [1]:
- untar the original tarball
- copy the debian directory inside the untarred upstream directory
- work on the package as usual
- build it using passing "-i.svn" option to dpkg-buildpackage or debuild
- once finished commit your changes to the debian directory directly
from the upstream tarball
- now you can remove the upstream tree and update the debian directory
outside the upstram tree
If you have suggestion on other ways to work I will be very happy :-) I
know that is not so handy but I don't want to commit the whole upstream
sources to the repository ...
----------- Remarks -----------
No changes should be done directly to the upstream sources, all changes
should be shipped in a debian/patches/ file.
It's more easy than you can think, have a look at the dpatch-edit-patch
command.
----------- Cheering -----------
Cheers.
----------- Foot notes -----------
[1] but you can obviously to as you want the important points are two:
- no changes outside the debian dir (use dpatch)
- the debian dir has to be committed at least at each debian revision of
the package so that everyone can work using only the repository
--
Stefano Zacchiroli -- Master in Computer Science @ Uni. Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} - http://www.bononia.it/zack/
" I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant! " -- G.Romney
Attachment:
pgplEXmYsEEuu.pgp
Description: PGP signature