From: yac <yac@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Thoughts on PIL and Pillow
Date: Tue, 28 May 2013 23:19:59 +0200 [thread overview]
Message-ID: <20130528231959.55f2ffd3@gentoo.org> (raw)
In-Reply-To: <20130528195840.2718704b@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Tue, 28 May 2013 19:58:40 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> On Tue, 28 May 2013 13:45:22 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>
> > The question I have: Is it better to have Pillow as a separate
> > package and set up a virtual, or should Pillow just be added as a
> > version bump of dev-python/imaging?
> >
> > The portage tree currently has both dev-python/imaging-2.0.0
> > (hard-masked), and dev-python/pillow-2.0.0. My intent was to
> > eliminate dev-python/pillow with a pkg move, but upon further
> > consideration I would like to gather some more opinions on the
> > matter.
>
> Moving forks onto original packages sounds much like Arfrever was
> doing in the past. That's why we have dev-python/setuptools which is
> not setuptools, doesn't it?
>
> Merging two unmerged projects into a single ebuild is a mess. Just
> keep them separate, make a virtual for it. When packages work with
> pillow, switch them to the virtual.
+1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-05-28 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 17:45 [gentoo-python] Thoughts on PIL and Pillow Mike Gilbert
2013-05-28 17:58 ` Michał Górny
2013-05-28 21:19 ` yac [this message]
2013-06-03 7:39 ` Arfrever Frehtes Taifersar Arahesis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130528231959.55f2ffd3@gentoo.org \
--to=yac@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox