| 1 |
On Fri, 2009-10-23 at 14:39 +0100, Alan Hourihane wrote: |
| 2 |
> On Fri, 2009-10-23 at 15:30 +0200, Fabian Groffen wrote: |
| 3 |
> > On 23-10-2009 14:28:17 +0100, Alan Hourihane wrote: |
| 4 |
> > > On Fri, 2009-10-23 at 15:14 +0200, Fabian Groffen wrote: |
| 5 |
> > > > On 23-10-2009 11:00:14 +0200, Fabian Groffen wrote: |
| 6 |
> > > > > On 23-10-2009 10:15:11 +0200, Markus Duft wrote: |
| 7 |
> > > > > > it seems that the code using os.pipe() seems either broken or the |
| 8 |
> > > > > > interix implementation of that python code is broken... whichever it is |
| 9 |
> > > > > > - it's bad ... :( |
| 10 |
> > > > > > |
| 11 |
> > > > > > Could you (grobian), please add "Interix" to the existing white list for |
| 12 |
> > > > > > openpty platforms? |
| 13 |
> > > > > |
| 14 |
> > > > > geez... Interix really sucks. Anyway, if you add it to 701, does it |
| 15 |
> > > > > work then, or does it hang in that case? |
| 16 |
> > > > |
| 17 |
> > > > hmm that check in portage looks totally broken to me, and makes |
| 18 |
> > > > sparc/solaris hang too... |
| 19 |
> > > |
| 20 |
> > > Which area is this as I've noticed FreeMiNT's emerging process takes |
| 21 |
> > > much longer at the moment. |
| 22 |
> > |
| 23 |
> > usr/lib/portage/pym/portage/__init__.py |
| 24 |
> > |
| 25 |
> > look for openpty |
| 26 |
> > |
| 27 |
> > there is a bit of code to test whether this can work or not also |
| 28 |
> > involving python 3.1 |
| 29 |
> |
| 30 |
> O.k. I'll take a look. |
| 31 |
|
| 32 |
This looks fine on FreeMiNT. |
| 33 |
|
| 34 |
I've still got two problems with the current portage though. |
| 35 |
|
| 36 |
1. Constantly updating mtimedb on every invocation of emerge. |
| 37 |
2. Very slow. |
| 38 |
|
| 39 |
Argh! |
| 40 |
|
| 41 |
Maybe I need to go back and find out which one it broke on. But I feel |
| 42 |
it's probably before 14487 which is the last in the tree. |
| 43 |
|
| 44 |
Alan. |
Archives