| 1 |
On 8/27/09, Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
> Moral of the story - don't trust portage to support your machine |
| 3 |
> tomorrow just because it works today, and don't expect portage |
| 4 |
> maintainers to care. The response you'll get, if you get one at all, |
| 5 |
> is 'be a man, create your own overlay, be responsible for your |
| 6 |
> machine, and shut up'. |
| 7 |
|
| 8 |
Given the possibly large-ish number of folks trying to run Gentoo on |
| 9 |
older hardware with similar problems, and given that there already are |
| 10 |
overlays for "bleeding edge" (qting-edge, kde-crazy, everything with |
| 11 |
live-scm ebuilds etc), maybe some of the old hw owners should organize |
| 12 |
a bit and try to pool their time into, e.g., a "grandpas-trusty" |
| 13 |
overlay with much of the old ebuilds easily available or something. |
| 14 |
|
| 15 |
I think it has already been suggested and considered that everything |
| 16 |
that gets removed from portage would instead get moved into some |
| 17 |
"old-stuff-dump" overlay, but I just don't have the time to look up |
| 18 |
any references and discussion over it right now ... |
| 19 |
|
| 20 |
Naturally it is not a perfect solution as bit-rot will inevitably get |
| 21 |
you when things like APIs and ABIs change enough, but just not having |
| 22 |
to hunt down everything from Attics (not to mention patch-packages and |
| 23 |
the original sources) into local overlays would probably be a |
| 24 |
considerable time-saver. |
| 25 |
|
| 26 |
But once again, it comes down to the question "ok, maybe it could |
| 27 |
work, who'll do it?" The regular devs seem to be pretty occupied given |
| 28 |
their current workload, so they might not have the extra oomph saved |
| 29 |
for this. |
| 30 |
|
| 31 |
-- |
| 32 |
Arttu V. |
Archives