1 |
On Mon, 18 Feb 2013 14:51:40 -0500 |
2 |
Mike Gilbert <floppym@g.o> wrote: |
3 |
|
4 |
> On Mon, Feb 18, 2013 at 2:44 PM, Michał Górny <mgorny@g.o> wrote: |
5 |
> > On Mon, 18 Feb 2013 13:09:40 -0500 |
6 |
> > Mike Gilbert <floppym@g.o> wrote: |
7 |
> > |
8 |
> >> I set up a mini-binhost in my devspace so that people can more easily |
9 |
> >> install pypy on lower-end hardware. |
10 |
> >> |
11 |
> >> Add one the following to your PORTAGE_BINHOST depending on your arch. |
12 |
> >> |
13 |
> >> http://dev.gentoo.org/~floppym/pypy/amd64/ |
14 |
> >> http://dev.gentoo.ogr/~floppym/pypy/x86/ |
15 |
> > |
16 |
> > Did you mean: ogre? |
17 |
> > |
18 |
> >> You should then be able to install pypy with emerge -g. |
19 |
> > |
20 |
> > Hmm, if you have both amd64 & x86, I think we should really consider |
21 |
> > deploying pypy-bin. |
22 |
> > |
23 |
> |
24 |
> Adding a separate pypy-bin package means we have to mess with the |
25 |
> eclasses to get the deps right. |
26 |
|
27 |
With python-r1 it should be quite simple. |
28 |
|
29 |
Does PMS permit things like: |
30 |
|
31 |
|| ( a b || ( c d ) e ) |
32 |
|
33 |
? AFAICS it doesn't prohibit it, saying that || () takes 'dependency |
34 |
atoms of any type'. |
35 |
|
36 |
> Also I have no idea how we would deal with PYTHON_REQ_USE. Maybe |
37 |
> use.force to implement fake use flags on pypy-bin? |
38 |
|
39 |
Yes, use.force is a good idea indeed. Or a virtual :P. |
40 |
|
41 |
> Overall, just reusing binpkgs seems simpler. |
42 |
|
43 |
For you, not for users :P. |
44 |
|
45 |
-- |
46 |
Best regards, |
47 |
Michał Górny |