On Friday 30 July 2010, 20:56:25 Martin Schlander wrote:
Fredag den 30. juli 2010 19:15:40 skrev Will
> On Friday 30 July 2010 19:03:28 Martin Schlander wrote:
> > it, so at least people
> _can_ get rid of it
> I think that's fairly safe; 4.5 falls back at runtime to the
> existing Phonon backends if pulseaudio is not present, and since we
> have this great abstraction layer, I don't see anyone making PA a hard
> dependency upstream.
> But how do we implement this at a packaging level? Just put it
> in the patterns? Make kdebase4-runtime Recommends: it? (NB this is a
> soft dep that can be broken, but that will be used by YaST and zypper
> to pull in the dep when installing kdebase4-runtime. I'm not sure if
> PA would be reinstalled if the user did a subsequent zypper dup without
> making PA taboo.
How about only starting the daemon (and insserv'ing it) on the first install
attempt only? (Isn't that the usual default of system services?)
If it does harm on a system, we can tell the user to stop the service. That
implies: as long as the daemon is dead, PA should behave as not being
I'm not sure what the best way to do it is.
But 'zypper dup' reinstalling it is not something I'd consider a problem.
If the user runs 'zypper dup' he forfeits whining privileges in my book.
Hmm, how do you do your usual update tasks with say a dozen repos containing
overlapping packages and be sure, that you get the most current ones?
zypper dup is the most useful zypper command, and I tend to believe, that
for those who run zypper directly, it's the most frequently used one, too.
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org