1 |
On Thu, Aug 27, 2009 at 8:36 AM, Arttu V.<arttuv69@×××××.com> wrote: |
2 |
> On 8/27/09, Mark Knecht <markknecht@×××××.com> wrote: |
3 |
>> Moral of the story - don't trust portage to support your machine |
4 |
>> tomorrow just because it works today, and don't expect portage |
5 |
>> maintainers to care. The response you'll get, if you get one at all, |
6 |
>> is 'be a man, create your own overlay, be responsible for your |
7 |
>> machine, and shut up'. |
8 |
> |
9 |
> Given the possibly large-ish number of folks trying to run Gentoo on |
10 |
> older hardware with similar problems, and given that there already are |
11 |
> overlays for "bleeding edge" (qting-edge, kde-crazy, everything with |
12 |
> live-scm ebuilds etc), maybe some of the old hw owners should organize |
13 |
> a bit and try to pool their time into, e.g., a "grandpas-trusty" |
14 |
> overlay with much of the old ebuilds easily available or something. |
15 |
> |
16 |
> I think it has already been suggested and considered that everything |
17 |
> that gets removed from portage would instead get moved into some |
18 |
> "old-stuff-dump" overlay, but I just don't have the time to look up |
19 |
> any references and discussion over it right now ... |
20 |
> |
21 |
> Naturally it is not a perfect solution as bit-rot will inevitably get |
22 |
> you when things like APIs and ABIs change enough, but just not having |
23 |
> to hunt down everything from Attics (not to mention patch-packages and |
24 |
> the original sources) into local overlays would probably be a |
25 |
> considerable time-saver. |
26 |
> |
27 |
> But once again, it comes down to the question "ok, maybe it could |
28 |
> work, who'll do it?" The regular devs seem to be pretty occupied given |
29 |
> their current workload, so they might not have the extra oomph saved |
30 |
> for this. |
31 |
> |
32 |
> -- |
33 |
> Arttu V. |
34 |
|
35 |
Yes, the 'who' is always a big question in open source, and the only |
36 |
reliable answer I've seen is 'the person who wants to', which |
37 |
unfortunately can change over time. |
38 |
|
39 |
It's not an answer to the whole problem as it wouldn't allow me to |
40 |
build an old machine from scratch but I'd love to see some little |
41 |
daemon that ran on my system and noticed when something I currently |
42 |
had installed was being removed from portage. If it see this it would |
43 |
automatically moved a copy of ebuilds and distfiles into some sort of |
44 |
a local 'in-use' overlay so they'd still be available to me on this |
45 |
machine. With something like that at least then nothing would be lost. |
46 |
Maybe then there's a little app to allow me to remove it from the |
47 |
overlay when I'm done wit it, or I'd do it by hand. |
48 |
|
49 |
What I dislike about the current system is some person out there in |
50 |
the ether deciding what's right for my hardware with the main criteria |
51 |
being what's easy for him. Yes, I can, by hand and with time and |
52 |
training, eventually find and replace things I need, but I have never |
53 |
thought the way it is working now was the right way. |
54 |
|
55 |
- Mark |