Re: Add to Library Support for F-spot and Banshee

Hash: SHA256

Joe Shaw wrote:
> Hi,
> On Sun, 2006-06-11 at 13:23 +0100, Daniel Drake wrote:
>> This is comparable to the enqueue operation we used to have for music files:
>> It was hardcoded to totem, and caused a few problems which affected a 
>> lot of users:
>> - Not all beagle users had totem installed
>> - There was no way to configure the enqueue action to make it use a 
>> different music player
> This is also the situation with the various mailers, because of the lack
> of a standard way of opening a specific email.  There is annoying if
> code in there depending on whether you use Evolution or KMail (or
> Thunderbird, if you're using the patch).  But email is so important that
> we have to use those hacks.
> Clearly "Enqueue" isn't that important, and my inclination that "Add to
> Library" isn't either.
> The patch is fine, but in the meantime I think this is a decision we
> have to leave up to the distributors.  For SUSE and SLED it makes sense
> for us to include the patch because we use beagle-search only on the
> GNOME side and Banshee and F-Spot are our default apps for this.  (On
> the KDE side there is Kerry and I think it already does a better job at
> integrating with the default KDE apps.)  Whether this is true for
> everyone, I'm not sure.  And the burden of maintaining those patches is
> there as well.
> Kevin, it definitely makes sense to keep around bugs for these.  Maybe
> we could have a tracking bug for this type of stuff so we can address it
> later (and so that people can get the patches).
Maybe we could start a 'patches' directory in CVS? It wouldn't be
included in the build, but that way we keep a centralized and version
controlled way to keep some patches like these, and to make packagers
more aware of their existence. I know its dangerous (since the burden to
maintain them falls more upon us) but its a mildly common practice.
(There's something like it in dashboard).

Just a thought, either way I'll make one master bug about 3rd party apps
and functions and make these 2 bugs dependant on it, so we have one bug
number/link to use.

Either way, whats the thought on making a 'For Packagers' page in the
wiki covering some of this stuff and any other notes. (Such as best
practice stuff on the debugging output and cronjobs for the static

Kevin Kubasik
Version: GnuPG v1.4.2.2 (GNU/Linux)


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