Currently, dev-python/django can't be installed with dev-python/pillow.
Please allow it to be built alongwith either one of dev-python/imaging or dev-python/pillow.
Does it work 'out of the box'?
I'm using =dev-python/imaging-2.0.0-r1000 from progress overlay which actually installs pillow. It's working fine for me.
I haven't tried with the pillow ebuild in portage.
Which means you are clearly reporting your issue to the wrong bug tracker. Even if we supported mixing Gentoo ebuilds with Progress overlay which we don't, Progress overlay will override the ebuilds for django if it doesn't already.
(In reply to Michał Górny from comment #3)
> Which means you are clearly reporting your issue to the wrong bug tracker.
> Even if we supported mixing Gentoo ebuilds with Progress overlay which we
> don't, Progress overlay will override the ebuilds for django if it doesn't
I think you misunderstood. Let me explain properly.
I want to install django with pillow. The gentoo ebuild for dev-python/django pulls in dev-python/imaging but the gentoo ebuild for dev-python/imaging blocks dev-python/pillow.
Now since =dev-python/imaging-2.0.0-r1000 from progress actually installs pillow instead of PIL, I let portage install it.
But I would rather mask dev-python/imaging & install dev-python/pillow from portage but since portage didn't allow me to do that, I went the other way to avoid the hassle of creating an ebuild in my local overlay.
Let's take another look at this.
I see two possible resolutions here: we either rename dev-python/pillow to dev-python/imaging, as Arfrever has done in progress overlay, or we create a virtual for this.
I'm leaning toward the former since the original PIL has not been updated since 2009.
Please use a virtual to keep things clean, these are technically two different packages.
(In reply to Matt Summers from comment #7)
> Please use a virtual to keep things clean, these are technically two
> different packages.
Perhaps I should retract this statement given that a virtual may not work in all cases due to the way things get imported.
|| ( dev-python/imaging dev-python/pillow ) should work in most cases I suspect, leave it to the user to know what they need. Thoughts?
(In reply to Matt Summers from comment #8)
I sent mail to the gentoo-python list soliciting feedback.
In the readme `pillow` is advertised to be a drop-in replacement.
There is a degree of incompatibility (like importing `Image` from the global namespace instead of `PIL`), but it's been deprecated for quite a while and also seems to be dropped from imaging 1.2 anyway.
It should be safe to rename.
I see that the virtual has been added to portage. So should this bug be marked resolved?