[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-xfce-devel] Welcome to pkg-xfce and SVN matters.

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 23, 2005 at 08:19:58PM +0100, Emanuele Rocca wrote:
> * [ 23-01-05 - 12:27 ] Andrew Lau <netsnipe@users.sourceforge.net> wrote:=
> >  As you can now tell, we now have an Alioth project and mailing list:
> >  <pkg-xfce-devel@lists.alioth.debian.org>.
> Cool. :)
> >  I've also taken the liberty of importing the current state xfce4-goodi=
> >  into our SVN repository at:
> >  http://svn.debian.org/wsvn/pkg-xfce
> [...]
> >  If you're wondering how this all works, read
> >  /usr/share/doc/gnome-pkg-tools/README.Debian.gz (which I co-wrote for
> >  the pkg-gnome project) or the much more comprehensive manual to
> >  svn-buildpackage.
> Ok, if I understand correctly it is necessary to keep only the debian/
> directory under svn, the original tarballs in ../tarballs/ and use
> simple-patchsys.mk from CDBS or dpatch in order to change the upstream
> sources.

Yes. That's correct. tarballs/ and build-area/ are kept locally and are
never to be uploaded.
> What do we think is the best choice? dpatch or CDBS?  Every package in
> -goodies already use CDBS, so I would go for it.  Opinions?

I've never used dpatch personally since simple-patchsys.mk is so much
easier. It's purely up to personal perference depending on how heavy
duty your patching needs to be.

The aim is to always keep each module/function patch separately instead
of having them all rolled up in one .diff.gz so as to make it a snap for
other co-maintainers to jump in and figure out what's going on or what
has been merged upstream in the next release and can be removed.

Andrew "Netsnipe" Lau

	Andrew "Netsnipe" Lau	<http://www.cse.unsw.edu.au/~alau/>
 Debian GNU/Linux Maintainer & UNSW Computing Students' Society President
		  "Nobody expects the Debian Inquisition!
     Our two weapons are fear and surprise...and ruthless efficiency!"

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

Version: GnuPG v1.2.5 (GNU/Linux)



Reply to: