From: "Nikolaj Sjujskij" <sterkrig@myopera.com>
To: "Michał Górny" <mgorny@gentoo.org>, "Mike Gilbert" <floppym@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] Binhost for pypy
Date: Tue, 19 Feb 2013 17:30:29 +0400 [thread overview]
Message-ID: <op.wsq843eqh7emz2@verkdatorn.npdb> (raw)
In-Reply-To: <CAJ0EP43KBaizR2k05D5pMwv6xWxvyMJvBaY5rC=o8_cW_N-9rw@mail.gmail.com>
Den 2013-02-18 23:51:40 skrev Mike Gilbert <floppym@gentoo.org>:
> On Mon, Feb 18, 2013 at 2:44 PM, Michał Górny <mgorny@gentoo.org> wrote:
>> On Mon, 18 Feb 2013 13:09:40 -0500
>> Mike Gilbert <floppym@gentoo.org> wrote:
>>
>>> I set up a mini-binhost in my devspace so that people can more easily
>>> install pypy on lower-end hardware.
>>>
>>> Add one the following to your PORTAGE_BINHOST depending on your arch.
>>>
>>> http://dev.gentoo.org/~floppym/pypy/amd64/
>>> http://dev.gentoo.ogr/~floppym/pypy/x86/
>>
>> Did you mean: ogre?
>>
>>> You should then be able to install pypy with emerge -g.
>>
>> Hmm, if you have both amd64 & x86, I think we should really consider
>> deploying pypy-bin.
>>
>
> Adding a separate pypy-bin package means we have to mess with the
> eclasses to get the deps right.
>
> Also I have no idea how we would deal with PYTHON_REQ_USE. Maybe
> use.force to implement fake use flags on pypy-bin?
>
> Overall, just reusing binpkgs seems simpler.
dev-lang/ghc has IUSE="binary" for similar purposes.
Prebuilt PyPy is great idea indeed.
prev parent reply other threads:[~2013-02-19 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:09 [gentoo-python] Binhost for pypy Mike Gilbert
2013-02-18 19:44 ` Michał Górny
2013-02-18 19:51 ` Mike Gilbert
2013-02-18 21:13 ` Michał Górny
2013-02-19 13:30 ` Nikolaj Sjujskij [this message]
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=op.wsq843eqh7emz2@verkdatorn.npdb \
--to=sterkrig@myopera.com \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@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