| 1 |
On Wed, 24 Jun 2009 13:17:12 -0700, Mark Knecht wrote: |
| 2 |
|
| 3 |
> 1) It absolutely isn't that the hardware is unsupported, it's that a |
| 4 |
> *feature* of the hardware (TV Out S-Video) became unsupported. |
| 5 |
|
| 6 |
And the S-Video output is part of the hardware, so you do have |
| 7 |
unsupported hardware. |
| 8 |
|
| 9 |
> 2) Following your Bugzilla suggestion about asking that it be put back |
| 10 |
> into portage to it's logical conclusion and it gets scary. Here's the |
| 11 |
> paraphrased request: |
| 12 |
> |
| 13 |
> a) I need ati-driver-8.28.8 put back into portage because it's the |
| 14 |
> last driver that supports TV out for the 9100 IGP chipset. |
| 15 |
> b) Unfortunately I need 2.6.19 added back into portage because it's |
| 16 |
> the last kernel that ati-driver-8.28.8 runs on. |
| 17 |
> c) Because all this old stuff doesn't work on the new xorg-server I |
| 18 |
> need xorg-server-1.1.1 to remain in portage. |
| 19 |
|
| 20 |
When you put it like that... but there's no harm in asking. |
| 21 |
|
| 22 |
> I really think this is what a personal overlay is for, but as I've |
| 23 |
> said for years, it's hard to build an overlay when you don't know what |
| 24 |
> needs to be in it until it's been removed. |
| 25 |
|
| 26 |
I think that whenever you start masking newer versions of a package to |
| 27 |
force portage to stay with the older ones, you should consider |
| 28 |
copying them to an overlay. Everything is removed eventually and if you |
| 29 |
can't keep up with updates, you preferred version will disappear at some |
| 30 |
time. It's not the end of the world as you can still get the files from |
| 31 |
the CVS attic, it's just that copying them in advance saves some work. |
| 32 |
|
| 33 |
> And yes, *something* has |
| 34 |
> removed these files, at least from my distfiles directory and I'm |
| 35 |
> pretty confident it wasn't me by hand because the machines all have |
| 36 |
> disk space which is the only reason I ever remove packages from there |
| 37 |
> by hand. |
| 38 |
|
| 39 |
eix-sync makes no mention of cleaning $DISTDIR, either in its man page or |
| 40 |
--help output, so I reckon you're running something else to do this. |
| 41 |
Maybe eclean in a postsync script. What do you have in |
| 42 |
/etc/portage/postsync.d? |
| 43 |
|
| 44 |
You could put a script in here that runs |
| 45 |
|
| 46 |
rsync -a /usr/portage/ /usr/portage.bak/ |
| 47 |
|
| 48 |
which would mean you have your own portage attic and could retrieve any |
| 49 |
deleted ebuild whenever you want. |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
Neil Bothwick |
| 54 |
|
| 55 |
Anything is possible if you don't know what |
| 56 |
you are talking about. |
Archives