From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Xmms needs to die.
Date: Thu, 24 Aug 2006 20:28:17 +0000 (UTC) [thread overview]
Message-ID: <ecl250$rof$2@sea.gmane.org> (raw)
In-Reply-To: Mahogany-0.67.0-10670-20060824-143125.00@kihnet.sk
Robert Cernansky <hslists2@zoznam.sk> posted
Mahogany-0.67.0-10670-20060824-143125.00@kihnet.sk, excerpted below, on
Thu, 24 Aug 2006 14:31:25 +0200:
> On Thu, 24 Aug 2006 20:39:10 +1000 Jonathan Adamczewski
> <jadamcze@utas.edu.au> wrote:
>
>> Robin H. Johnson wrote:
>> > don't take XMMS away from those of us already using it without any
>> > issues.
>>
>> It can disappear from portage without affecting your ability to keep
>> using it.
>
> Not true, when upgrading world I'll always get message like:
>
> !!! Ebuilds for the following packages are either all !!! masked or don't
> exist:
> media-sound/xmms
>
> And --depclean will be broken because it will want to remove all xmms
> dependencies. Maybe there are other issues with installed¬_in_portage
> packages.
That's what overlays (local or public/general) are for. There's normally
a 30-day period the ebuild is masked, during which that warning will
appear with the 30-day explanation from profiles/package.mask, giving you
the chance to act accordingly and move it to your overlay, listing it in
package.unmask. When the 30 days is over and it's removed from portage,
you still have it in your overlay.
Even if you don't sync and update during those 30 days and the ebuild is
removed from the tree, given that it's installed, you'll still have an
ebuild for it in /var/db/pkg/, and if you use FEATURES=buildpkg (as I do)
for backup purposes, you'll also have the ebuild attached to the end of
the binpkg tarball. (I used that a couple times before I realized the
ebuild was already in /var/db/pkg.)
Even if you lose your local copies, the ebuild will still be available
from Gentoo's viewCVS for some time, where it can be retrieved from the
attic.
All that said, I too use xmms as I've yet to find anything else as simple
and reliable that continues to "just work". It's very possibly the only
thing I have merged here still using gtk1, but while that means getting
rid of it would mean I'd be able to unmerge gtk1, it also means there's
little else that could break it or that it could break, thru the common
gtk1 dependencies, now. I'd very much like it to continue working for
years yet.
/That/ said, there remains the reality of a now unmaintained gtk1, making
it harder and harder for Gentoo to continue to support thru successive
toolchain update iterations. If no one's willing to continue to maintain
xmms /and/ ultimately gtk1... it will of necessity eventually die.
When it dies in Gentoo, while users can maintain it in their overlays for
months, the clock is seriously ticking, as more and more incompatibilities
between it and a kept-current system pile up.
... Personally, I'm hoping xmms will remain at least until KDE4 comes
around, with hopefully something there more workable than the KDE3 and
other solutions I've tried -- but kept returning to xmms, because it "just
worked", and didn't require undue resources to do it. Getting arts out of
the way as the main KDE audio framework will be a big part of that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-24 20:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 20:30 [gentoo-dev] Xmms needs to die Luis Medinas
2006-08-23 20:47 ` Ioannis Aslanidis
2006-08-24 0:07 ` Mike Frysinger
2006-08-24 2:49 ` Luis Medinas
2006-08-24 2:58 ` Alec Warner
2006-08-24 3:11 ` Josh Saddler
2006-08-24 3:32 ` Luis Medinas
2006-08-24 0:00 ` [gentoo-dev] " Christian 'Opfer' Faulhammer
2006-08-24 9:44 ` Luis Medinas
2006-08-24 4:33 ` [gentoo-dev] " Luca Barbato
2006-08-24 13:12 ` Stephen P. Becker
2006-08-24 16:23 ` Dominique Michel
2006-08-24 19:37 ` Luca Barbato
2006-08-24 19:48 ` Stephen P. Becker
2006-08-24 19:57 ` Ciaran McCreesh
2006-08-24 22:41 ` Stephen P. Becker
2006-08-25 14:41 ` bret curtis
2006-08-24 20:07 ` Luca Barbato
2006-08-24 4:44 ` Mike Frysinger
2006-08-24 6:40 ` Richard Fish
2006-08-24 7:01 ` Jakub Moc
2006-08-24 13:34 ` Anders Hellgren
2006-08-24 12:19 ` Robert Cernansky
2006-08-24 13:16 ` Pierre Guinoiseau
2006-08-24 13:53 ` Robert Cernansky
2006-08-24 14:01 ` Krzysiek Pawlik
2006-08-24 14:22 ` Robert Cernansky
2006-08-24 15:08 ` Andrej Kacian
2006-08-24 16:42 ` Robert Cernansky
2006-08-24 16:55 ` Adriaan Leijnse
2006-08-24 17:34 ` Andrej Kacian
2006-08-25 7:03 ` Robert Cernansky
2006-08-27 17:46 ` Doug Goldstein
2006-08-27 20:51 ` Ciaran McCreesh
2006-08-27 21:08 ` Doug Goldstein
2006-08-24 18:46 ` Alec Warner
2006-08-25 7:05 ` Robert Cernansky
2006-08-26 15:04 ` Paul de Vrieze
2006-08-26 17:00 ` Alec Warner
2006-08-26 20:07 ` Luis Francisco Araujo
2006-08-26 17:46 ` Josh Saddler
2006-08-26 18:03 ` Luis Medinas
2006-08-27 8:11 ` Robert Cernansky
2006-08-27 8:26 ` Mike Frysinger
2006-08-27 21:50 ` [gentoo-dev] " Duncan
2006-08-25 9:35 ` [gentoo-dev] " Christian Birchinger
2006-08-25 17:20 ` Steve Dibb
2006-08-25 18:38 ` [gentoo-dev] " Duncan
2006-08-25 20:49 ` [gentoo-dev] " Alec Warner
2006-08-25 20:59 ` Luis Medinas
2006-08-27 8:04 ` Robert Cernansky
2006-08-24 12:21 ` Robin H. Johnson
2006-08-24 10:39 ` Jonathan Adamczewski
2006-08-24 12:31 ` Robert Cernansky
2006-08-24 20:28 ` Duncan [this message]
2006-08-24 10:46 ` Luis Medinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ecl250$rof$2@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox