svn2cl implementations (was: Re: version number (was: Re: r112 - trunk))

[Joost van Baal]

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

On Thu, Mar 25, 2004 at 11:32:36AM +0100, Peter Palfrader wrote:
> On Thu, 25 Mar 2004, Laurent Fousse wrote:
>=20
> > Le Thu, Mar 25, 2004 at 10:32:56AM +0100, Peter Palfrader =E9crivait:
> > > The version issue should be fixed now, can you test?
> >=20
> > svn2cl ./ChangeLog
> > make: svn2cl: Command not found
> > make: *** [ChangeLog] Error 127
> >=20
> > This svn2cl is something that need to be done once as the tarball is
> > released, right ? (because I wouldn't like to build-depend on a python
> > script :-)
>=20
> Can't we just ship the svn2cl script in the repository?  At least the
> perl version seems short enough, and the python version isn't much
> longer.

I prefer the python version, since it uses svn log's xml output: this is
likely much more robust.  The perl version will break when the svn log
output format has subtle changes.

I prefer not to stick such a scrip in our repository: developers should
keep there systems up to date themselves.  I don't think the script will
be kept up to date if it's stuck in our repository.  Furthermore,
shipping it in our repository causes a higher risk on a fork of the
script.

Filing a RFP would be better :)

Bye,

Joost


--m+utxuhC6KVTvgNz
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)

iD8DBQFAYrouBgac8paUV/ARAljkAJ4xDq8nZqh5cjfK4PMOSp85iD5ErACbBKS2
ZVmE0QIDZW+cQdhBRXi8S+A=
=ly5N
-----END PGP SIGNATURE-----

--m+utxuhC6KVTvgNz--