Re: Why do we disable esd in libgnome?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 2, 2009 at 6:56 AM, Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote:
> On Mon, 02.02.09 07:49, King InuYasha (ngompa13@xxxxxxxxx) wrote:
>
>> But when you break something as major as libgnome, steps should be taken to
>> ease the transition. Perhaps the function could be forwarded? I'm not really
>> much of a programmer, but I recognize that you can't just break
>> functionality in core libraries like that and expect everyone to fix their
>> apps up "just like that." Fowarding the function (for compatibility
>> purposes) while deprecating it would probably be more ideal. In any case,
>> that's just my two cents...
>
> For a core piece of an API keeping compat is certainly important. But
> this is sound events, don't forget that. Quite frankly, most people have them
> deatcivated anyway.
>
> It has been documented that this can be disabled at compile time and
> it's pretty unimportant anyway and there is a much better replacement
> available. Hence I'd assume that the advantage of getting rid of this
> legacy cruft will always be more attractive then keeping it around.

What about the possibility of rewriting gnome_sound* to use libsydney?
I know it's not the most exciting work available, but that would some
to be the correct long term fix. It's not like the libgnome API can go
away prior to GNOME-3.0.

--
Dan

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux