Uploading experimental pwlib/openh323 to unstable

[Jose Carlos Garcia Sogo]

--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

El d=EDa 04 may 2004, Mark Purcell escrib=EDa:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Jose,
>=20
> Thanks for the work on gnugk.

  No problem. I only don't want it to be lost because of manty and you
  don't using SVN ;-)

> I'm still a bit behind the curve on Subversion, so I will take a while to=
 get=20
> upto speed. Also I have only needed cvs in the past to get read-access to=
=20
> projects in development.
>=20
> That said I see the Debian use of Subversion a great step forward, please=
 just=20
> give me some time to get upto speed with the change of Package maintenanc=
e=20
> philosophy.

  Ok, no problem. My "problem" is that I usually can only devote long
  periods of time to Debian stuff at weekends, so what is not done in a
  weekend usually means that will need another week to be completed.
  BTW, Kilian and me are very interested in having a way of contacting
  you other than email, perhaps jabber IM or so. This is more important
  as your timezone is not so "compatible" with ours.

>=20
> I'm currently working my way through your README and have managed to down=
load=20
> the archive. =20
>=20
> I just now have to work out how to make changes, get them committed back =
to=20
> the archive and then carry out the package building process.

  They way that most people work with this type of SVN repo is to make
  changes directly in debian/ dir in the repo, compile the package,
  check that everything is fine, commit changes and upload the package.
  If you need to commit changes but you're not going to upload a package
  (because you're not going to devote any time to the package in some
  days, or you want to let other people work or know what you're working
  on, you should set in changelog the release name to UNRELEASED)

  If a lot of changes are needed, usually it worths capying debian/ out
  of the repo to the sources, making changes and copying debian/ dir
  back to the repo.

>=20
> Is there any other documentation on how to use subversion in a Debian con=
text?
>=20
> The documentation under /usr/share/doc/svn-buildpackage looks like a good=
=20
> 'tutorial' start for how/ why to use Subversion under Debian.

  This is a nice doc, but have into account that it aims to keeping
  _all_ upstream source into SVN. In my own experience with CVS repos
  for packages, keeping upstream source is prone to errors, as when you
  inject a new version, new sources are silently merged with any change=20
  you have made in a previous one, which sometimes is not so good.
  Having those changes in a file within debian/patches, you can easily
  check which files are going to be patched.

  Cheers,

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAmBEoS+BYJZB4jhERAos/AKC3x0rjEOXW0Oh+Ba7d3TvDcfWInwCeI2ZA
XbEVPxJXAPSSJeK5Zvf4BTc=
=c2S6
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--