emerging gimp-print, I get the message at the and of this entry. Then if I do: emerge -C gimp emerge gimp-print emerge --nodeps gimp everything works fine! I mean I can print from gimp (either 2.2.10, or 9999) So why this message??? I want to use gimp-print-5.0.0_rc2 because of better support for my printers and it also saves some ink :-) ============================================================== * gimpprint is not yet available due to the API Change in version 5.0 * Please remerge gimp with USE=-gimpprint to avoid collissions !!! ERROR: media-gfx/gimp-print-5.0.0_rc2 failed. Call stack: ebuild.sh, line 1910: Called dyn_setup ebuild.sh, line 653: Called pkg_setup !!! gimp with gimpprint USE-flag detected !!! If you need support, post the topmost build error, and the call stack if relevant. emerge --info: Portage 2.1_pre4-r1 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r2, 2.6.14-gentoo x86_64) ================================================================= System uname: 2.6.14-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ Gentoo Base System version 1.12.0_pre15 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -march=k8" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -pipe -march=k8" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://a/portage" USE="amd64 X a52 aac aalib alsa ansi avi berkdb bitmap-fonts bitmapfonts breakme bzip2 cdparanoia cdr cjk clisp crypt css cups dar32 dar64 dbus dpms dri dv dvd dvdr dvdread dvi eds emacs emboss encode exif f77 faac faad ffmpeg flac foomaticdb fortran gcj gif gimp gimpprint gkrellm gnome gnuplot gpm grammar gstreamer gtk gtk2 gtkhtml imagemagick imlib ipv6 java javascript jpeg jpeg2k kde lame lapack latex lcd lcms leim libgda lzw lzw-tiff mad mailbox math matroska mbox mng mozilla mp3 mpeg musepack musicbrainz nautilus ncurses nls nptl nptlonly nsplugin ogg oggvorbis opengl oss pam pdf pdflib perl png ppds python qt quicktime rar readline reiserfs rtc sdl smp speex spell ssl svg t1lib tcltk tcpd tetex tga theora thesaurus tiff truetype truetype-fonts type1-fonts unicode usb vcd vorbis wmf wordperfect xine xpm xv xvid zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LANG, LC_ALL, LDFLAGS, LINGUAS
Because the things collide with each other, that's exactly what the message says. Kindly see Bug 95358.
(In reply to comment #1) > Because the things collide with each other, that's exactly what the message > says. Kindly see Bug 95358. > My point is that they DO NOT collide. You can safely compile them together, ignoring the fact, that ebuild now prevents it. Actually my trick above worked last week, this week I cant get gimp-print to compile with gimp-2.2.10. It still works with gimp-9999. The bug you are referring to, is from the times that this didn't work, but it works now! At least it worked for me last few months :-) Bottom line is I don't mind that someone made gimp depending on gimp-print-4.X, as long as I can compile gimp-print-5.0.0_rc2 after the gimp and everything works fine with the new gimp-print. Now someone changed ebuilds so I can't do this anymore :-( So maybe this qualifies for a bug report ??
