Discussion of Gnome Clipboard Manager (gcm) development

Re: Access to cvs.gnome.org?

On Wed, 2003-02-05 at 14:07, Andrew Lau wrote:
> Dear Philip,
> 	Have you transferred any of our CVS accounts from SourceForge
> to GNOME CVS yet? I think it would also be a good idea to empty out
> our repository on SourceForge and leave just a single README there so
> no one in future accidentally works on obsolete code.

Hi there Andrew, I have transfered a few accounts from sourceforge to
GNOME Cvs. I while a go I asked who wanted a account and I remember two
persons asked for such a account. I can, of course, always ask for more
accounts. Please let me know if somebody needs a account. 

I think clearing out the sourceforge cvs is a good idea. However, we
will have to file a request for that.. you can remove all files but they
will still exist in the Attic directory. You are free to do this; I
think your rights are high enough to ask for this.

Please leave the old gcm directory or make the cvs admins move it to
"gcm-old" or something like that. I dont keep backups of the old version
of gcm and maybe somebody wants a version someday? It's the only gtk1.2
clipboard manager that I know of ...

You are, of course, also free to commit changes to the GNOME Cvs if your
account works (I remember creating a account for you?). This includes
fixes for automake. Of course, always make sure that such changes work
on non-debian platforms too. Debian is great but gcm is not a
debian-only application of course . Such debian-specific changes
belong to your package-patches afaik. I will always notice such issues
as I use RedHat 8.0 for desktop usage.

(Continue reading)

headers

Andrew Lau | 5 Feb 16:59

Re: Access to cvs.gnome.org?

Hi Philip,

On Wed, Feb 05, 2003 at 02:54:52PM +0100, Philip Van Hoof wrote:
> Hi there Andrew, I have transfered a few accounts from sourceforge to
> GNOME Cvs. I while a go I asked who wanted a account and I remember two
> persons asked for such a account. I can, of course, always ask for more
> accounts. Please let me know if somebody needs a account. 

Oh yes, you're right. I do have an account = ). Thanks!

> You asked for the versions of ..... and .... : well I use the versions
> shipped by RedHat 8.0. 

http://www.redhat.com/software/linux/technical/packages.html

autoconf 	2.53 	A GNU tool for automatically configuring source code.
autoconf213 	2.13 	A GNU tool for automatically configuring source code.
automake 	1.6.3 	A GNU tool for automatically creating Makefiles.
automake14 	1.4p6 	A GNU tool for automatically creating Makefiles.
automake15 	1.5 	A GNU tool for automatically creating Makefiles.

I can tell you're using automake-1.4 judging from the symlinks to
install-sh, missing etc you have, but which version of autoconf are
you using?  Will you be upgrading gcm to use autoconf 2.53 and
automake 1.6 in the near future, or would it break too much stuff and
take too much effort?

Yours sincerely,
Andrew "Netsnipe" Lau

(Continue reading)

headers

Philip Van Hoof | 5 Feb 17:09

Re: Access to cvs.gnome.org?

On Wed, 2003-02-05 at 16:59, Andrew Lau wrote:

> 
> Oh yes, you're right. I do have an account = ). Thanks!

np :)

> > You asked for the versions of ..... and .... : well I use the versions
> > shipped by RedHat 8.0. 
> 
> http://www.redhat.com/software/linux/technical/packages.html
> 
> autoconf 	2.53 	A GNU tool for automatically configuring source code.
> autoconf213 	2.13 	A GNU tool for automatically configuring source code.
> automake 	1.6.3 	A GNU tool for automatically creating Makefiles.
> automake14 	1.4p6 	A GNU tool for automatically creating Makefiles.
> automake15 	1.5 	A GNU tool for automatically creating Makefiles.

[freax <at> snuffel icons]$ automake --version
automake (GNU automake) 1.6.3
Written by Tom Tromey <tromey <at> redhat.com>.

Copyright 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
[freax <at> snuffel icons]$

But check the autogen.sh script; it invokes the automake selected by

(Continue reading)