| 1 |
Mike Frysinger wrote: |
| 2 |
> |
| 3 |
> that certainly sounds reasonable to me. if the stable cant be maintained, let |
| 4 |
> the common workflow of developers transition it back to ~arch until someone |
| 5 |
> has the time to keep arch usable. changing profiles.desc accordingly should |
| 6 |
> be done ahead of time. perhaps a new category for profiles.desc ? "exp" for |
| 7 |
> such ports ? i could see all *-fbsd ports being moved there. tweak repoman |
| 8 |
> to be less verbose about dep issues for such profiles and we're set. |
| 9 |
|
| 10 |
Sounds like a plan. 'exp' would be the 'status' field? I need to remove |
| 11 |
2006.1, as that profile has been a big holdup due to it not being glibc-2.4 |
| 12 |
friendly (or one of the newer glibcs back in that era; I forget). Even |
| 13 |
pondering just outright booting 2007.0, as I've been using 2007.1-dev since I |
| 14 |
commited it long ago, and haven't had an issue with it really. I can then put |
| 15 |
2008.0-dev together and use it as a launch platform for ~arch migration. |
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
> i see dropping keywords as a very last resort. getting a port *back* into the |
| 20 |
> tree is a *tremendous* amount of work (i went through it and it was hell), |
| 21 |
> while keeping ~arch alive is a sliver of effort and generally not a blocker |
| 22 |
> for package maintainers. |
| 23 |
|
| 24 |
Aye, I believe that was sh's removal and subsequent re-add? |
| 25 |
|
| 26 |
Part of the hangup lately has been our kernel support. O2 systems are dead in |
| 27 |
the water in 2.6.24, and only work in 2.6.23 if you apply a hack to serial_core |
| 28 |
(a hack that only masks a problem rather than fixes it). Octane's I can still |
| 29 |
forward port, but with the upstream author having moved onto other interests, if |
| 30 |
something breaks badly enough from one version to the next, then I run the risk |
| 31 |
of getting stuck on a particular version permanently. |
| 32 |
|
| 33 |
Indigo2 R10000's may wind up getting resurrected, as support for that is |
| 34 |
actually headed into upstream now, so it'll be the end of patching for that |
| 35 |
system. Though the gcc patch needs fixing. |
| 36 |
|
| 37 |
And I'm really considering dropping our mips3 (Indigo2/Indy R4x00) support to |
| 38 |
cut back on the number of stages and netboots pumped out (-3 and -1, |
| 39 |
respectively, when they get pumped out). R4x00 is an odd CPU, with a ton of |
| 40 |
variations, and of them, only the R4400 ever seems to work well at all. |
| 41 |
|
| 42 |
The hard part is finding time and motivation. My attention span lately has been |
| 43 |
worse than a goldfish's. That said, however, profiles should be doable come the |
| 44 |
weekend, at least for removing 2006.1, renaming 2007.1, and pondering 2007.0's fate. |
| 45 |
|
| 46 |
|
| 47 |
--Kumba |
| 48 |
|
| 49 |
-- |
| 50 |
Gentoo/MIPS Team Lead |
| 51 |
|
| 52 |
"Such is oft the course of deeds that move the wheels of the world: small hands |
| 53 |
do them because they must, while the eyes of the great are elsewhere." --Elrond |
| 54 |
-- |
| 55 |
gentoo-dev@l.g.o mailing list |
Archives