On Mon, 2009-03-09 at 15:23 +0200, Ted Gould wrote:
> On Sun, 2009-03-08 at 21:25 -0400, Cory K. wrote:
> > Scott Kitterman wrote:
> > > On Sat, 07 Mar 2009 14:57:13 +0000 Ted Gould <firstname.lastname@example.org> wrote:
> > >> That makes sense to me, but I'm not as sure about how all that works.
> > >> Perhaps we could discuss this with everyone at the next Ubuntu Desktop
> > >> meeting? I think that'd probably be a good place to work out the
> > >> dependencies correctly.
> > >
> > > I'm not generally at those meetings, so I can't say if the right people
> > > would be there or not. My thought is that if it's decided that
> > > notifications should be part of the 'standard' pidgin experience then the
> > > package should recommend the standard library for providing it.
> > As someone that manages a derivative (Ubuntu Studio) this is one change
> > (though we are currently testing notify-osd) we don't want forced on us
> > as a recommend. We already have mixed feedback from our users.
> I'm confused now
> All I'd really like is for the default experience that people get is
> that they get Pidgin configured to work well with notify-osd. How it
> gets packaged to do that is not my expertise.
> Can someone suggest the best way to do that in a way that works well for
> derivates? I'm quite sure I don't understand all the packaging issues
If this is such an issue on non-GNOME DEs, how about making
ubuntu-desktop recommend pidgin-libnotify? Right now, it seems that
ubuntu-desktop recommends pidgin and pidgin-otr, so it should be a
trivial issue to add pidgin-libnotify to this list.
Chow Loong Jin
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel