| 1 |
Robert Cernansky <hslists2@××××××.sk> posted |
| 2 |
Mahogany-0.67.0-10670-20060824-143125.00@××××××.sk, excerpted below, on |
| 3 |
Thu, 24 Aug 2006 14:31:25 +0200: |
| 4 |
|
| 5 |
> On Thu, 24 Aug 2006 20:39:10 +1000 Jonathan Adamczewski |
| 6 |
> <jadamcze@××××××××.au> wrote: |
| 7 |
> |
| 8 |
>> Robin H. Johnson wrote: |
| 9 |
>> > don't take XMMS away from those of us already using it without any |
| 10 |
>> > issues. |
| 11 |
>> |
| 12 |
>> It can disappear from portage without affecting your ability to keep |
| 13 |
>> using it. |
| 14 |
> |
| 15 |
> Not true, when upgrading world I'll always get message like: |
| 16 |
> |
| 17 |
> !!! Ebuilds for the following packages are either all !!! masked or don't |
| 18 |
> exist: |
| 19 |
> media-sound/xmms |
| 20 |
> |
| 21 |
> And --depclean will be broken because it will want to remove all xmms |
| 22 |
> dependencies. Maybe there are other issues with installed¬_in_portage |
| 23 |
> packages. |
| 24 |
|
| 25 |
That's what overlays (local or public/general) are for. There's normally |
| 26 |
a 30-day period the ebuild is masked, during which that warning will |
| 27 |
appear with the 30-day explanation from profiles/package.mask, giving you |
| 28 |
the chance to act accordingly and move it to your overlay, listing it in |
| 29 |
package.unmask. When the 30 days is over and it's removed from portage, |
| 30 |
you still have it in your overlay. |
| 31 |
|
| 32 |
Even if you don't sync and update during those 30 days and the ebuild is |
| 33 |
removed from the tree, given that it's installed, you'll still have an |
| 34 |
ebuild for it in /var/db/pkg/, and if you use FEATURES=buildpkg (as I do) |
| 35 |
for backup purposes, you'll also have the ebuild attached to the end of |
| 36 |
the binpkg tarball. (I used that a couple times before I realized the |
| 37 |
ebuild was already in /var/db/pkg.) |
| 38 |
|
| 39 |
Even if you lose your local copies, the ebuild will still be available |
| 40 |
from Gentoo's viewCVS for some time, where it can be retrieved from the |
| 41 |
attic. |
| 42 |
|
| 43 |
All that said, I too use xmms as I've yet to find anything else as simple |
| 44 |
and reliable that continues to "just work". It's very possibly the only |
| 45 |
thing I have merged here still using gtk1, but while that means getting |
| 46 |
rid of it would mean I'd be able to unmerge gtk1, it also means there's |
| 47 |
little else that could break it or that it could break, thru the common |
| 48 |
gtk1 dependencies, now. I'd very much like it to continue working for |
| 49 |
years yet. |
| 50 |
|
| 51 |
/That/ said, there remains the reality of a now unmaintained gtk1, making |
| 52 |
it harder and harder for Gentoo to continue to support thru successive |
| 53 |
toolchain update iterations. If no one's willing to continue to maintain |
| 54 |
xmms /and/ ultimately gtk1... it will of necessity eventually die. |
| 55 |
|
| 56 |
When it dies in Gentoo, while users can maintain it in their overlays for |
| 57 |
months, the clock is seriously ticking, as more and more incompatibilities |
| 58 |
between it and a kept-current system pile up. |
| 59 |
|
| 60 |
... Personally, I'm hoping xmms will remain at least until KDE4 comes |
| 61 |
around, with hopefully something there more workable than the KDE3 and |
| 62 |
other solutions I've tried -- but kept returning to xmms, because it "just |
| 63 |
worked", and didn't require undue resources to do it. Getting arts out of |
| 64 |
the way as the main KDE audio framework will be a big part of that. |
| 65 |
|
| 66 |
-- |
| 67 |
Duncan - List replies preferred. No HTML msgs. |
| 68 |
"Every nonfree program has a lord, a master -- |
| 69 |
and if you use the program, he is your master." Richard Stallman |
| 70 |
|
| 71 |
-- |
| 72 |
gentoo-dev@g.o mailing list |
Archives