Re: ocaml package on SVN
On Sun, Jun 08, 2003 at 05:31:31PM +0200, Stefano Zacchiroli wrote:
> On Sun, Jun 08, 2003 at 04:50:48PM +0200, Sven Luther wrote:
> > > 1) is ok to you to move the policy on SVN? It was one of the original
> > > proposal for SVN (and we used it asking for the repository :-)
> >
> > Please go ahead, use the policy package from
> > http://people.debian.org/~luther/ocaml/ocaml_packaging_policy though, or
> > the one from my 3.06-17 package.
>
> Done downloading the web version:
>
> pkg-ocaml-maint/policy/trunk/ocaml_packaging_policy
>
> Please perform next modifications there [1]
Ok, i will.
If someone would want to adapt it for future inclusion in the official
debian policies, they are welcome.
> > > 2) I remember from a previous thread that you would like to move the
> > > ocaml package on SVN, right?
> >
> > Yep, but i have not had the time to read-up on SVN, nor will i have in
> > the next time. If you could be so kind as to put the 3.06-16 source
> > package into SVN, i would then check in my 3.06-16 modifications.
> >
> > Now, i see from the diagram above that you only wanted to put the debian
> > directory into SVN, and that you finally also moved the orig tarball.
> > Would it not make better sense for ocaml to contain the whole unpacked
> > tree ? And in this case to have a upstream and a trunk directory ?
>
> Yes, it's a possibility but I would like to avoid committing all
> upstream sources each time a new release comes out. This is for me one
> of the major disadvantages with other tools such as cvs-buildpackage.
Mmm,
> Anyway I guess that ocaml package has a lot of changes to upstream
> sources and switching to dpatch require a bit of time. I can perform the
> migration if you like, but only if you next decide (and if you like) to
> use SVN and dpatch otherwise is useless ...
For next release i plan to use dpatch, that is put all the changes to
debian source in a subdirectory of debian, and apply them at build time.
I would prefer not to use a tarball as XFree86 uses, since this would
mean loosing the md5sum of the upstream tarball, but i guess this is
doable.
If we go this way, i would do the dpatching myself for 3.07. I don't
know if it would be worthwill to do this for 3.06 still, as said, i hope
we can ship 3.07 with sarge.
> > BTW, How did you adapt to Paris ?
>
> Fine thanks, I've also met Jerome, Ralf and other local DDs at a First
> Jeudi meeting; if you have a week end or so to travel to Paris we will
> be glad to meet with you.
Yep, i will be more often in paris starting starting from july, so this
would be easier. Maybe i can even be there for next FirstJeudi meeting,
i don't know.
> Cheers.
>
> [1] Just a reminder because you haven't yet played with SVN:
> - checkout (create a "trunk" dir in your current dir containing the
> policy)
> svn co svn+ssh://pkg-ocaml-maint.alioth.debian.org/svn/pkg-ocaml-maint/policy/trunk
> - modify and commit as with CVS
> (but using "svn" command instead of "cvs" :-PPPP)
> - subversion use an hidden ".svn" directory instead of a "CVS" visible
> one so beware not to include that directory in the ocaml package
Erm, i suppose the correct way is to do a svn export for releasing a new
package, which would not include those .svn directories, right ?
Friendly,
Sven Luther
Reply to: