The GIMP CMYK plugin. Have fun. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 14719 [details] media-gfx/gimp-cmyk-0.1.ebuild
Created attachment 14741 [details] media-gfx/gimp-cmyk-0.1.ebuild Small beautification, adjusting default icc color profile paths.
Created attachment 32105 [details] media-gfx/gimp-cmyk this ebuild: 1. depends media-gfx/adobe-iccprofiles (well you need a cymk color profile for this to work anyway...) 2. enable system-wide CC & CFLAGS 3. strips the executable 4. fix paths in platform_unix.h patch follows.
Created attachment 32106 [details, diff] gimp-cmyk-0.1-fixpath.patch put in ${FILESDIR}/0.1, else previus ebuild might not work.
Hrmm, this looks useful.
Version 0.3 Many thanks to: Sven Neumann for doing much of the work involved in cleaning up and porting the plugin to GIMP 2.0. Is there a chance tu update ebuild? During installation I got : >>> Emerging (2 of 4) media-gfx/gimp-cmyk-0.1 to / * separate.gimp20.tar.gz MD5 ;-) ... [ ok ] * separate.gimp20.tar.gz RMD160 ;-) ... [ ok ] * separate.gimp20.tar.gz SHA1 ;-) ... [ ok ] * separate.gimp20.tar.gz SHA256 ;-) ... [ ok ] * separate.gimp20.tar.gz size ;-) ... [ ok ] >>> Creating Manifest for /usr/local/portage/media-gfx/gimp-cmyk * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking separate.gimp20.tar.gz ;-) ... [ ok ] >>> Unpacking source... /var/tmp/portage/gimp-cmyk-0.1/work >>> Unpacking separate.gimp20.tar.gz to /var/tmp/portage/gimp-cmyk-0.1/work /usr/local/portage/media-gfx/gimp-cmyk/gimp-cmyk-0.1.ebuild: line 34: epatch: command not found >>> Source unpacked. >>> Compiling source in /var/tmp/portage/gimp-cmyk-0.1/work/separate.gimp20 ... make: O2: Polecenie nie znalezione make: O2: Polecenie nie znalezione make: O2: Polecenie nie znalezione Package gimp-1.3 was not found in the pkg-config search path. Perhaps you should add the directory containing `gimp-1.3.pc' to the PKG_CONFIG_PATH environment variable No package 'gimp-1.3' found Package gimpui-1.3 was not found in the pkg-config search path. Perhaps you should add the directory containing `gimpui-1.3.pc' to the PKG_CONFIG_PATH environment variable No package 'gimpui-1.3' found /bin/sh: separate.o: command not found make: *** [separate] Błąd 127 strip: 'separate': No such file >>> Source compiled. >>> Test phase [not enabled]: media-gfx/gimp-cmyk-0.1 >>> Install gimp-cmyk-0.1 into /var/tmp/portage/gimp-cmyk-0.1/image/ category media-gfx * dummy install. we'll do this later wz gimptool-2.0. >>> Completed installing gimp-cmyk-0.1 into /var/tmp/portage/gimp-cmyk-0.1/image/ man: >>> Merging media-gfx/gimp-cmyk-0.1 to / * Installing gimp-cmyk (separate) with gimptool-2.0... Error: Couldn't find file to build/install/uninstall >>> Regenerating /etc/ld.so.cache... >>> media-gfx/gimp-cmyk-0.1 merged. >>> Recording media-gfx/gimp-cmyk in "world" favorites file... >>> No packages selected for removal by clean. Of Cource it was installed with success but with those errors above I think I won't work at all.
sorry for writing under: http://www.blackfiveservices.co.uk/projects/separate-gimp2-0.3_linux.tar.gz
Created attachment 98855 [details] Updated ebuild I'm not a coder but I wanted to install this updated gimp-cmyk and tarted playing with gimp-cmyk-0.1.ebuild untill I saw plugin seprate in gimp plugin browser :)
http://www.blackfiveservices.co.uk/separate.shtml gimp-cmyk-0.3 has been released
(In reply to comment #9) > http://www.blackfiveservices.co.uk/separate.shtml > > gimp-cmyk-0.3 has been released > This release was present in october;)
Either find a maintainer, or if you want to maintain it yourself, feel free to reopen and join project sunrise, details here: http://www.gentoo.org/proj/en/sunrise Thanks. WONTFIX.
Created attachment 192601 [details] Updated to use separate+-0.5.3 Updated ebuild to the new code version. This ebuild won't install properly without the installer.patch (see next attachment). I plan to submit to sunrise.
Created attachment 192603 [details] patch to fix install part of Makefile This patch creates the destination directory during the install process (something that wasn't done via upstream, since install by default puts everything into directories GIMP creates upon install)
Submitted to sunrise as media-gfx/gimp-cmyk-plugin
PS -- this seems to work great with GIMP-2.6 (I haven't seen anyone else mention it)
Created attachment 229825 [details] ebuild for 0.5.7 0.5.7 is out now, and it compiles and works fine for me with the attached ebuild and a renamed (to 0.5.7) files/0.5.5-Makefile.patch. My only changes were a changed download path, a better description and more accurate dependencies: --- gimp-cmyk-plugin-0.5.5.ebuild 2010-04-30 20:49:58.000000000 +0200 +++ gimp-cmyk-plugin-0.5.7.ebuild 2010-04-30 20:59:29.000000000 +0200 @@ -7,9 +7,9 @@ inherit eutils multilib toolchain-funcs MY_P="separate+-${PV}" -SFNUM="42977" +SFNUM="46785" -DESCRIPTION="Gimp CMYK plug-in." +DESCRIPTION="The Separate+ GIMP CMYK plug-in." HOMEPAGE="http://cue.yellowmagic.info/softwares/separate.html" SRC_URI="mirror://sourceforge.jp/separate-plus/${SFNUM}/${MY_P}.zip http://download.adobe.com/pub/adobe/iccprofiles/win/AdobeICCProfilesCS4Win_end-user.zip" @@ -19,10 +19,10 @@ KEYWORDS="~amd64 ~x86" IUSE="" -RDEPEND="media-libs/lcms +RDEPEND=">=media-libs/lcms-1.18 media-libs/jpeg media-libs/tiff - media-gfx/gimp" + >=media-gfx/gimp-2.4" DEPEND="${RDEPEND}" S="${WORKDIR}/${MY_P}" Could someone maybe upload this ebuild (and the renamed patch) to sunrise? Also I think it would be nice if the bug could be reopened because it IS in sunrise now (and a maintainer would still be appreciated).
And also maybe this should go from media-gfx to media-plugins? Maybe someone else could clarify on the exact meaning of the categories.
Reopening as the ebuild is in Sunrise.
Created attachment 259821 [details] ebuild for 0.5.8
Created attachment 259823 [details, diff] patch to 0.5.8
Created attachment 409182 [details] new ebuild proposal for 0.5.8 depend on lcms:2 (see related Makefile patch)
Created attachment 409184 [details, diff] new patch proposal for 0.5.8 for lcms:2 add lm to linked libs
Created attachment 409186 [details] updated ebuild proposal for 0.5.8 keep gentoo-specific hack in ebuild and everything else in FILESDIR patch
Created attachment 409188 [details, diff] updated patch proposal for 0.5.8 force compile against lcms2 add libm to linking phase
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
The project Web page appears to be gone, the last time it got updated on sourceforge.jp was in 2010, and I have found reports of it not working with gimp-2.10. It seems https://cyan.fxarena.net/ is the way to go for CYAN support in the GIMP nowadays. Is there still any interest in adding this to the tree? If not, we shall close this ticket in 30 days.
(In reply to Marek Szuba from comment #26) > The project Web page appears to be gone, the last time it got updated on > sourceforge.jp was in 2010, and I have found reports of it not working with > gimp-2.10. It seems https://cyan.fxarena.net/ is the way to go for CYAN > support in the GIMP nowadays. > > Is there still any interest in adding this to the tree? If not, we shall > close this ticket in 30 days. Well, having cyan in tree would be great. It looks great, has active dev... What's not to like?
Looks like packaging Cyan will be the way to go. Closing this one.
