Sam Hocevar | 6 Jun 13:20
Gravatar

Bug#185090: gcm_2.0.4-2(unstable/ia64): FTBFS: cannot find library

   libgnomeui (2.2.0.1-2.0.1), which is a rebuild, fixes the issue. You
can either build-depend on (>=2.2.0.1-2.0.1) specifically on ia64, or
build-depend on (>=2.2.1-1) which has just been uploaded.

--

-- 
Sam.

-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
Philip Van Hoof | 6 Jun 21:04

The future


A .NET version ..

This .. will be the future of GNOME Clipboard Manager.

Note that I don't care a lot if you dislike the fact that I am going to
rewrite it in .NET and that I will add Mono and Gtk-Sharp as dependancy.
This is what I want to do .. so it's my choice whatsoever. 

However, I will support your actions if you want to co-maintain the
C-version of GNOME Clipboard Manager versions 1.0 and 2.0.

GNOME Clipboard Manager 3.0 will be

GNOME Clipboard Manager 3.0 .Net

And will require Mono as dependancy

Why? Because C#, .NET and Mono rule and I dislike maintaining C
applications.

Plans :

- Clipboard Manager Deamon
 - Network transparant

- Editor client
- StatusDock client
- Hotkey client

(Continue reading)

haran | 8 Jun 06:28
Picon

Re: The future

On 6 Jun 2003, Philip Van Hoof wrote:

> Why? Because C#, .NET and Mono rule and I dislike maintaining C
> applications.
Sound reasoning =)
I realize that I'm not going to change your mind but I'm wondering what 
are the specific advantages of using Mono that out-weight the fact that
gcm now has a costly dependency.

> 
> Plans :
> 
> - Clipboard Manager Deamon
>  - Network transparant
> 
> - Editor client
> - StatusDock client
> - Hotkey client
> 
> My RedHat packager has no problems adding Mono as dependancy (he keeps a
I've been wondering for some time and this seems as good a place as any to 
ask:
How do you get your software package into a distribution like RedHat or 
Debian?

Thanks.

-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
(Continue reading)

Philip Van Hoof | 8 Jun 10:59

Re: The future

On Sun, 2003-06-08 at 06:28, haran wrote:
> On 6 Jun 2003, Philip Van Hoof wrote:
> 
> > Why? Because C#, .NET and Mono rule and I dislike maintaining C
> > applications.
> Sound reasoning =)

> I realize that I'm not going to change your mind but I'm wondering what 
> are the specific advantages of using Mono that out-weight the fact that
> gcm now has a costly dependency.

- A garbage collector which means that I don't have to care about memory
issues anylonger

- A very good OO programming language C#

- Platform independancy (if Mono -and Gtk+ support the platform of
course)

- C# is much more easy to maintain compared to C

- A very rich Framework that just works in stead of 100 different
libraries that clash and don't work well together

> > My RedHat packager has no problems adding Mono as dependancy (he keeps a

> I've been wondering for some time and this seems as good a place as any to 
> ask:
> How do you get your software package into a distribution like RedHat or 
> Debian?
(Continue reading)

Philip Van Hoof | 8 Jun 17:45

the module ..


http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/gcm/Gcm.Net/

Note that it does not work yet ;).. but that is the initial revision

--

-- 
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
work: Philip dot VanHoof at cronos dot be
http://www.freax.be, http://www.freax.eu.org

-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
Andrew Lau | 9 Jun 17:57

Re: The future

On Fri, Jun 06, 2003 at 09:04:25PM +0200, Philip Van Hoof wrote:
> By the time Gcm.Net is ready I quess that Debian will have put mono
> in it's main apt-mirrors too ?!

Hey Philip,
	Glad to see you back working on gcm! Mono is still not
officially supported by Debian GNU/Linux yet, but there are test
packages of Mono 0.23 and Gtk# 0.8 at the moment from the Debian Mono
Packaging Team [1]. These packages will become official eventually, so
I will be building gcm.net with them. It might even be a good idea for
me to have them host gcm.net Debian packages until Mono is uploaded
into Debian so that users will need to only add one extra apt source.
	By the way, could you please release whatever we have in CVS
for a 2.1.x tarball before the wait for gcm.net begins? gcm 2.0.4 did
have a few show stopping bugs in its compile scripts which probably
didn't leave a good impression in some people who otherwise be
enthusiastic testers/contributors.

[1] http://www.debianplanet.org/mono/

Yours sincerely,
Andrew "Netsnipe" Lau

--

-- 
----------------------------------------------------------------------
* Andrew "Netsnipe" Lau         Computer Science & Student Rep, UNSW *
*   # apt-get into it            Debian GNU/Linux Package Maintainer *
*    <netsnipe(+)debianplanet.org\0>   <alau(+)cse.unsw.edu.au\0>    *
* 1024D/2E8B68BD: 0B77 73D0 4F3B F286 63F1  9F4A 9B24 C07D 2E8B 68BD *
----------------------------------------------------------------------
(Continue reading)

Philip Van Hoof | 9 Jun 18:13

Re: The future

On Mon, 2003-06-09 at 17:57, Andrew Lau wrote:

> On Fri, Jun 06, 2003 at 09:04:25PM +0200, Philip Van Hoof wrote:
> > By the time Gcm.Net is ready I quess that Debian will have put mono
> > in it's main apt-mirrors too ?!

> Hey Philip,
> 	Glad to see you back working on gcm! Mono is still not
> officially supported by Debian GNU/Linux yet, but there are test
> packages of Mono 0.23 and Gtk# 0.8 at the moment from the Debian Mono
> Packaging Team [1]. These packages will become official eventually, so
> I will be building gcm.net with them. It might even be a good idea for
> me to have them host gcm.net Debian packages until Mono is uploaded
> into Debian so that users will need to only add one extra apt source.
> 	By the way, could you please release whatever we have in CVS
> for a 2.1.x tarball before the wait for gcm.net begins? gcm 2.0.4 did
> have a few show stopping bugs in its compile scripts which probably
> didn't leave a good impression in some people who otherwise be
> enthusiastic testers/contributors.

Well.. the .NET version of GCM is VERY unfinished business at this
moment Andrew. Thinking about packages and what needs to be packaged is
very very early at this moment.

I also don't yet know how to correctly distrubute Mono applications. You
could take a look at monodoc/browser and mono-debugger to see how Ximian
is planning to do this. Another thing that I don't know yet are
translations ..

I will probably not use auto*-tools and I already prepared the
(Continue reading)

Andrew Lau | 9 Jun 18:17

Re: The future

Dear Philip,

You still haven't answered my question about a 2.1 release to tie up
loose ends! = P

Cheers,
Andrew "Netsnipe" Lau

--

-- 
----------------------------------------------------------------------
* Andrew "Netsnipe" Lau         Computer Science & Student Rep, UNSW *
*   # apt-get into it            Debian GNU/Linux Package Maintainer *
*    <netsnipe(+)debianplanet.org\0>   <alau(+)cse.unsw.edu.au\0>    *
* 1024D/2E8B68BD: 0B77 73D0 4F3B F286 63F1  9F4A 9B24 C07D 2E8B 68BD *
----------------------------------------------------------------------
Philip Van Hoof | 9 Jun 19:06

Re: The future

On Mon, 2003-06-09 at 18:17, Andrew Lau wrote:
> Dear Philip,
> 
> You still haven't answered my question about a 2.1 release to tie up
> loose ends! = P

Well, if somebody really wants to release a 2.1 version .. then I don't
have any problems at all with that..

The fact is, however, that "I" am not a good releaser ;). I always screw
something up. And.. I also don't care a lot about releases; IMHO my work
stops at the CVS-version.

So, Andrew, if you want to release a 2.1 version or maybe even maintain
the 2.x branch then that's fine for me. Just send me the tar.gz and
inform Dag Wieers about your release ... or just ask me for access on
the sourceforge pages (or can you already write files there?)

Also note that you may fix stuff .. if you can write on the cvs. If you
can't (it's on the GNOME cvs server) then ask me and I'll ask for a
cvs-account on the gnome-cvs .. or send me patches and I "will" commit
those.

The main reason why I have not worked on GCM for a long time is because
really "nobody" is fixing stuff and "everybody" is wining about broking
buildscripts and broken features which are (this is what they say) are
soooo easy to fix ;) .. well start fixing...

cvs -u diff > file.patch

(Continue reading)

Philip Van Hoof | 16 Jun 20:04

Re: gcm: patch

Thanks and committed to CVS

On Mon, 2003-06-16 at 19:56, Mark Finlay wrote:
> Hey Philip
> 
> patch against the c version of gcm to turn off beeping by default.
> 
> I can explain why if should be turned off if you like, but wont
> bother unless you want me too cus I'm mad busy
--

-- 
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
work: Philip dot VanHoof at cronos dot be
http://www.freax.be, http://www.freax.eu.org

-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

Gmane