Bug 47983 – New Package Submission: The Gimp-2.0.1 Ebuild

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Kevin Miller 2004-04-15 16:30:18 UTC]

Please find the attached gimp-2.0.1.ebuild for The Gimp-2.0.1

It should be located in media-gfx/gimp

This ebuild is an edited version of gimp-2.0.0.ebuild

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Kevin Miller 2004-04-15 16:31:42 UTC]

Created attachment 29383 [details]
gimp-2.0.1.ebuild

[Comment 2 Heinrich Wendel (RETIRED) 2004-04-17 04:50:54 UTC]

please post a patch if you change anything, otherwise just say that's the same ebuild

[Comment 3 Priit Laes (IRC: plaes) 2004-04-28 09:18:15 UTC]

Simple version bump... renaming to 2.0.1 works fine for me...

[Comment 4 Donovan Long 2004-05-01 22:23:08 UTC]

A bit more is needed than simply coping the 2.0.0 ebuild as the patches will fail without some modification of the ebuild.

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *   /usr/portage/media-gfx/gimp/files/gimp-2.0.1-gcc34.patch

The ebuild attached works here, let's get it into portage...

[Comment 5 Robert Brinson 2004-05-03 14:43:11 UTC]

I have also used the gimp-2.0.0.ebuild to create a gimp-2.0.1 ebuild. The only thing I did differently from the posted ebuild was to comment out the two patches mentioned in src_unpack(). I did this as I did not have a previous version of the gimp installed, I am using the current stable version of gcc, not gcc 3.4. Anyway, I put the ebuild in /usr/local/portage, created the PORTDIR_OVERLAY var in /etc/make.conf, downloaded the sources into /usr/portage/distfiles, and did an ebuild gimp-2.0.1.ebuild digest. I emerged gtkglarea, pygtk(~x86), libgtkhtml, and librsvg. Finally, I was able to successfully emerge gimp-2.0.1. It would be great to see an official ebuild of gimp-2.0.1, even if it is masked.

[Comment 6 foser (RETIRED) 2004-05-12 06:12:38 UTC]

*** Bug 50756 has been marked as a duplicate of this bug. ***

[Comment 7 Heinrich Wendel (RETIRED) 2004-05-29 03:24:42 UTC]

any status on this foser?

[Comment 8 Bret Towe 2004-06-02 19:33:13 UTC]

coping over the ebuild and patchs seems to make it work fine on my system

[Comment 9 foser (RETIRED) 2004-06-05 06:47:40 UTC]

*** Bug 53033 has been marked as a duplicate of this bug. ***

[Comment 10 Anders Rune Jensen (RETIRED) 2004-06-15 08:09:44 UTC]

gimp 2.0.2 was just released :-)

[Comment 11 Brian Harring (RETIRED) 2004-06-16 19:22:28 UTC]

Is there a particular holdup for keywording gimp x86?

[Comment 12 Brian Harring (RETIRED) 2004-06-16 19:24:27 UTC]

Err, rephrasing, moving 2.0.0 into stable.  Asking since it comes up quite often, and quite a few people have made the transition already via package.keywords.

[Comment 13 Thomas Weidner 2004-06-19 05:46:59 UTC]

the gimp-2.0.0 compiles and runs fine here, when simply renaming to gimp-2.0.2.ebuild and removing the gcc3.4 patch. it doesn't seem to be neccessary any more. pls update

[Comment 14 foser (RETIRED) 2004-06-21 15:19:11 UTC]

*** Bug 54573 has been marked as a duplicate of this bug. ***

[Comment 15 foser (RETIRED) 2004-06-21 16:33:38 UTC]

gimp-2.0.2 added... still fixme surrounding autodetection stands, I (obviously) don't have the time to fix that myself.

2.0.0 is x86