Bug#517921: Add wrapper script gimp-remote for backwards compatability

2009-03-03 Thread Ari Pollak
Sven Marnach wrote: > It's an interface change in the GIMP, and it's just good practice to > remain backward compatible. Applications would have to check the > version of the GIMP and call either gimp or gimp-remote depending on > that version. This is much more cumbersome than simply adding the

Bug#517921: Add wrapper script gimp-remote for backwards compatability

2009-03-03 Thread Sven Marnach
Ari Pollak schrieb am Mo, 02. Mär 2009, um 18:00:23 -0500: > Why can't the applications just fix which program they call? It's an interface change in the GIMP, and it's just good practice to remain backward compatible. Applications would have to check the version of the GIMP and call either gimp

Bug#517921: Add wrapper script gimp-remote for backwards compatability

2009-03-02 Thread Ari Pollak
Why can't the applications just fix which program they call? On Mon, 2009-03-02 at 22:12 +0100, Sven Marnach wrote: > Package: gimp > Version: 2.6.5-1 > Severity: wishlist > > As of version 2.6, gimp-remote is no longer necessary since gimp will > check for running instances automatically. Since

Bug#517921: Add wrapper script gimp-remote for backwards compatability

2009-03-02 Thread Sven Marnach
Package: gimp Version: 2.6.5-1 Severity: wishlist As of version 2.6, gimp-remote is no longer necessary since gimp will check for running instances automatically. Since some applications rely on gimp-remote (for example gqview in default configuration), it would be nice to have some wrapper scrip