ConsoleKit and esound retirement

[Lennart Poettering]

On Tue, 12.02.13 12:38, Jon Ciesla (limburgher at gmail.com) wrote:

> On Tue, Feb 12, 2013 at 12:34 PM, Lennart Poettering
> <mzerqung at 0pointer.de>wrote:
> 
> > Heya,
> >
> > since a while now logind has replaced CK in Fedora. I'd like to retire
> > it entirely from the distribution now.
> >
> > Most deps on CK are gone. Holdouts are "cdm", "lightdm", "lxsession",
> > "lxdm".
> >
> > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> >
> > This page doesn't say anything about retiring packages other still
> > depend on...
> >
> > I am tempted to just retire CK ignoring the remaining dependencies, in
> > the hope this will put the pressure on the folks involved to update
> > their stuff...
> >
> > Getting rid of CK in those packages is dead simple BTW. Just disable it
> > in the packages, but make sure pam_systemd is in the PAM stack for your
> > greeter tool. It's basically about removing code, not about adding
> > new code -- adding new code is only necessary if you want to improve
> > your DM to handle multi-seat setups, too (which is a new feature of
> > logind, not available in CK[1]). For details, see:
> >
> > http://www.freedesktop.org/wiki/Software/systemd/writing-display-managers
> >
> > I'd also like to retire "esound" finally. Currently, adplay, ayttm,
> > dopewars, e16, gnome-libs, gnubg, lxdream, moon-buggy, spacechart,
> > xarchon, xmms-esd still use it. esd of course has been deprecated and
> > dead since many years, the packages which still use it really should
> > wake up one day. So here, too, I'd just like to retire the package...
> >
> > Alternatively, somebody else can take these over, but honstely I'd
> > rather see them removed than continue to bitrot in our repository...
> 
> So to clarify, you're not actually retiring anything currently, just
> expressing to the community that you'd like to and that we should work
> toward making that possible?

Well, I am just checking before I do something whether I can actually do
it. That's all. By next week or so I will either have retired the
packages (which I'd prefer) or somebody else took them over (which I'd
prefer not to do, but which we can do too, if the retro-computing folks
step up...)

> If so, do you have any guidelines on getting rid of esound requirements?

Dunno really. My suspicion is that the packages in question are either
obsolete on their own, or should just be compiled with --disable-esd or
so. These packages all look pretty much esoteric or obsolete to me, so I
am not really that curious what precisely packagers would need to do...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.