[arch-commits] CVS update of unstable/multimedia/gimp-devel (3 files)

Eric Belanger belanger at ASTRO.UMontreal.CA
Sun Mar 2 21:43:54 UTC 2008


On Sun, 2 Mar 2008, Jan de Groot wrote:

> On Sun, 2008-03-02 at 00:12 -0500, Eric Belanger wrote:
> > Date: Sunday, March 2, 2008 @ 00:12:33
> >   Author: eric
> >     Path: /home/cvs-unstable/unstable/multimedia/gimp-devel
> >
> >    Added: ChangeLog (1.1)
> > Modified: PKGBUILD (1.18 -> 1.19) gimp-devel.install (1.4 -> 1.5)
> >
> > upgpkg: gimp-devel 2.4.5-1
> >
> >
> > --------------------+
> >  ChangeLog          |    5 +++++
> >  PKGBUILD           |    8 ++++----
> >  gimp-devel.install |    9 ++-------
> >  3 files changed, 11 insertions(+), 11 deletions(-)
>
> Why do you maintain 2.4.5 in unstable as -devel version? 2.4.5 is a
> stable version.
>
>

This is because a developement branch is not always available. Before gimp
2.4 was released, gimp stable was at 2.2.X and there was a 2.3.X
developpement brach. When gimp 2.4 was released, gimp-devel was
technically out-of-date. So users of gimp-devel had to replace it by gimp
and check whenever gimp-devel would be updated to switch back to the devel
branch. For convenience, I decided to use for gimp-devel the latest
released source tarball whether it's stable or developement.  That seems
the most convenient/logical way: users who want to stick with the stable
release use gimp and the ones who don't mind using a devel branch, uses
gimp-devel.  This is only temporary until a gimp 2.5 branch is released.

Last time, they released gimp 2.3 five months after 2.2.  As 2.4 was
released last October, I guess they'll release a 2.5 branch sometime this
month or in the next one.

Eric

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





More information about the arch-commits mailing list