public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why has xmms been killed suddenly?
Date: Wed, 25 Oct 2006 04:25:52 +0200	[thread overview]
Message-ID: <200610250425.52243.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <982e82bf0610241748u67b05f1fp794986bc9ce591a2@mail.gmail.com>

On Wednesday 25 October 2006 02:48, Ric de France wrote:
> On 24/10/06, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de> 
wrote:
> > And there is a rule about unmaintained packages with dead upstream and
> > working successors: they get killed.
> >
> > Everybody who reads gentoo-dev once in a while knew, that this day would
> > come - and nobody should really be surprised.
>
> It appears that the ebuild has been deleted off the portage tree...
> What would be the "safe" way to remove this and to move to another
> player? Does "emerge -C xmms" still work?

yes it does. When you emerge something, a copy of the ebuild is stored 
in /var/db/pkg/<category>/<nameofapp>/

(if you want to 'rescue ebuilds of removed but installed packages, just copy 
them).

a safe way:
emerge --unmerge xmms (and xmms-plugins and accesoires)

emerge --newuse --deep world

emerge playerofchoice
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-25  2:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24  7:08 [gentoo-user] Why has xmms been killed suddenly? local account for liebichw
2006-10-24  7:57 ` Hemmann, Volker Armin
2006-10-25  0:48   ` Ric de France
2006-10-25  2:25     ` Hemmann, Volker Armin [this message]
2006-10-25  3:43       ` Ric de France
2006-10-25  8:28         ` Neil Bothwick
2006-10-24  8:00 ` Dale
2006-10-24 13:06   ` Bira
2006-10-24 15:14     ` Mark Shields

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=200610250425.52243.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --cc=gentoo-user@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