empathy is a telepathy IM client, where the functionality is dependant on telepathy plugins installed. This ebuild is a meta-ebuild which pulls in empathy, and depending on the keywords, the appropriate telepathy plugins. Reproducible: Always Steps to Reproduce:
Created attachment 141037 [details] empathy-meta-0.0.1.ebuild My meta-package ebuild for empathy. (Version number is essentially random)
note to self, kick some voip guy to get telepathy-salut in portage.
It should probably full tp-haze too... as well as tp-sofiasip.
What about renaming it to telepathy-plugins-meta and making empathy depend on it? There are(will be) many different packages using telepathy that could take advantage of this meta package.
(In reply to comment #4) > What about renaming it to telepathy-plugins-meta and making empathy depend on > it? > > There are(will be) many different packages using telepathy that could take > advantage of this meta package. > That sounds better. CC'ed interested parties.
Comment #4 sounds exactly what we did for gstreamer with gst-plugins-meta and I like it. There we just have totem and similar things depend on that, it has all the USE flags for core sound/video stuff (oss, alsa, esound, etc) so that when you want to add a plugin, you just add the USE flag globally or for that meta, and you don't have to rebuild totem and all other gstreamer users with --newuse for no reason (plus this also means easier maintenance as it's just one place to add/change stuff). The same approach sounds like a good idea for telepathy as well, though I think it's not so loosely coupled as gstreamer plugins (e.g, new empathy could use telepathy backend specific UI for each protocol) - but could put the major protocols USE flag in the meta only that most can use, and the rare ones in the very few packages that use it, in that case. CCing tester too - maybe whole voip and/or net-im team might be interested though.
Having a tp-meta package sounds like a good idea. It should probably depends on farsight with the proper use flags too..
scratch that depending on farsihgt, I meant telepathy-stream-engine. Now that empathy has a release with voip enabled by default that kinda works most of the time.
If it's a meta-ebuild, why has it ~x86 keywords? And there are spaces missing near the "(" and ")" at the irc and bonjour lines.
*** Bug 236170 has been marked as a duplicate of this bug. ***
jingle support also reqrires telepathy-stream-engine, see #236170
I will add this, with a name like net-voip/telepathy-connection-managers unless anyone yells very loudly
(In reply to comment #12) > I will add this, with a name like net-voip/telepathy-connection-managers unless > anyone yells very loudly > This is a good idea. It this still not in tree yet?
net-voip/telepathy-connection-managers is there!