Re: important: automatic mirroring to the gimp cvs

2000-01-28 Thread Sven Neumann
Hi, Ok. I've just enabled automatic mirroring from the sourceforge cvs back to the gimp cvs. The file gimp/PLUGIN_CVS in the cvs tree controls which paths are mirrored and which are not. If anything goes havoc just delete that file and the script will stop doing anything. At the

Plugins at Sourceforge

2000-01-28 Thread Garry R. Osgood
In ChangeLog : Fri Jan 28 01:16:35 CET 2000 Marc Lehmann [EMAIL PROTECTED] * PLUGIN_CVS: updated to give Kevin Turner write access to the maze plug-in (therefore, the maze plug-in is no longer managable within the gnome cvs server. If you have any

PDB_PASS_THROUGH

2000-01-28 Thread Kelly Lynn Martin
I can find no evidence that this is actually used anywhere in the GIMP. Anybody know what it's for and whether it even works? Kelly

Re: Plugins at Sourceforge

2000-01-28 Thread Zach Beane - MINT
On Fri, Jan 28, 2000 at 05:29:48PM +0100, Marc Lehmann wrote: [snip] However, since the masses haven't cried out yet, I guess we can try and see how it works in practise. Count this as a cry out against it. I suggest waiting for a logical pause in development, such as the release of GIMP

Re: Plugins at Sourceforge

2000-01-28 Thread Glyph Lefkowitz
On Fri, 28 Jan 2000, Zach Beane - MINT wrote: On Fri, Jan 28, 2000 at 05:29:48PM +0100, Marc Lehmann wrote: [snip] However, since the masses haven't cried out yet, I guess we can try and see how it works in practise. Count this as a cry out against it. I suggest waiting for a

Re: Plugins at Sourceforge

2000-01-28 Thread Kelly Lynn Martin
On Fri, 28 Jan 2000 21:40:56 +0100, Marc Lehmann [EMAIL PROTECTED] said: One possible reason is that it is a pain in the ass to install additional plug-ins. Some things, like translations, must be part of the distribution currently. This needs to be fixed. :) Kelly

Re: Print plug-in

2000-01-28 Thread Kelly Lynn Martin
On Fri, 28 Jan 2000 18:03:32 -0500, Federico Mena Quintero [EMAIL PROTECTED] said: (As for footprint, well, the GIMP is not terribly lightweight either) :-) GIMP's a lot lighter than gnome-libs. I would substantially oppose any serious dependence on gnome-libs in GIMP. Especially since

Re: Plugins at Sourceforge

2000-01-28 Thread Kelly Lynn Martin
On Fri, 28 Jan 2000 23:47:25 +0100, Marc Lehmann [EMAIL PROTECTED] said: Most (but of course not all) of the problems are related to the fact that the menus are too full and can'T be changed, not necessarily that too many plug-ins are installed (which is mostly a diskspace problem). One of the

Re: Print plug-in

2000-01-28 Thread Federico Mena Quintero
We might also choose to use the upcoming Gnome Print System if it turns out to fit our needs and appears to be portable to non-Linux systems. As long as it doesn't require actually running Gnome (works with bare X, KDE, etc.) and its footprint is reasonably light, that sounds

Re: Print plug-in

2000-01-28 Thread Robert L Krawitz
Date: Fri, 28 Jan 2000 18:03:32 -0500 From: Federico Mena Quintero [EMAIL PROTECTED] CC: [EMAIL PROTECTED] If a GNOME program does not run under "bare" X or KDE, then it is broken and should be fixed. Do you have any examples of such programs? No; I just wanted to make

Re: Plugins at Sourceforge

2000-01-28 Thread Marc Lehmann
On Fri, Jan 28, 2000 at 02:36:36PM -0700, "Michael J. Hammel" [EMAIL PROTECTED] wrote: They do make it moderately easy during installation, but the default installations include lots of things many users will never need. But This is not at all a distribution issue. Linux is a *multi*-user

Re: Plugins at Sourceforge (fwd)

2000-01-28 Thread Michael J. Hammel
Thus spoke Zach Beane - MINT On Fri, Jan 28, 2000 at 05:29:48PM +0100, Marc Lehmann wrote: [snip] However, since the masses haven't cried out yet, I guess we can try and see how it works in practise. Count this as a cry out against it. I suggest waiting for a logical pause in

Re: Plugins at Sourceforge

2000-01-28 Thread Michael J. Hammel
Thus spoke Kelly Lynn Martin My position is sourceforge should be used at this time only for plug-ins which are not already in the source tree. Such plug-ins will not be a part of 1.2 anyway because 1.2 is frozen at this time. When 1.3 development begins, we can decide what to do with the