search

emesene / emesene-supported-plugins

set of plugins supported by the emesene team
http://www.emesene.org
15 stars 11 forks source link

Adding Supported Plugins Packages to PPA #9

Closed Mystro256 closed 12 years ago

Mystro256 commented 13 years ago

Just a suggestion

Perhaps adding a package in the ppa that installs the supported plugins automatically would be a good idea?

Any thoughts?

c10ud commented 13 years ago

yep, we need a way to make user access plugins easily..we need to have some advice from packagers

Mystro256 commented 13 years ago

Hmmm well pidgin actually has separate plugin packages thats included in the official distribution repositories. E.g. pidgin-musictracker

Although a link to download the supported plugins (and supported themes too) in the blog would be a good start; I don't think it's obvious where the the plugins are located unfortunately.

Mystro256 commented 13 years ago

I just commited some instructions into the README file, and a made a pull request along with some other stuff. Hopefully this helps make things clearer.

Continuing on what I said before, do you think it would be a good idea to add a link to the git on download page? Actually, it maybe a good idea to add all the gits to the code page, no?

kerosyn commented 13 years ago

For emesene supported, I say just just include them in the monthly packages. If they are updated during the middle of the month, users can manually update or just wait for updated plugins with the new release. Already added a commented out option for plugins in my windows installer script.

Community plugins for the time being should be manually downloaded, which for now means none.

Mystro256 commented 13 years ago

That seems like a good idea, who's in charge of the stable ppa?

kerosyn commented 13 years ago

Just wondering, is the plugins folder in the emesene root folder going to be used for anything now that there is one in the config?

Mystro256 commented 13 years ago

@syst3mfailur3 One is for all users, one is for individual users. I'm not sure about windows or mac, but this is the purpose/functionality in Linux.

kerosyn commented 13 years ago

So would the one in the emesene directory be a good location for emesene supported plugins and the other for community? On Jun 14, 2011 12:47 AM, "Mystro256" < reply@reply.github.com> wrote:

@syst3mfailur3 One is for all users, one is for individual users. I'm not sure about windows or mac, but this is the purpose/functionality in Linux.

Reply to this email directly or view it on GitHub:

https://github.com/emesene/emesene-supported-plugins/issues/9#issuecomment-1363823

Mystro256 commented 13 years ago

@syst3mfailur3 Well the purpose is for one is for universal plugins and the other is for personalized ones. When you have a computer with several different users, there can be use to this but it can be redundant for single user computers. Say I wanted to use some experiment plugins, which I would rather not let my wife use on her own user on this computer. That would be a situation where I would want to put plugins specifically in my config folder to avoid her enabling one by accident. Due to the config folder being in the user directory, it only can be used by that user. It's just like how some windows programs ask "install for all users?" when installing.

On Linux theres another advantage for single user computers; the root folder is protected by root privileges, while the config folder is free use. Either one of these can be an advantage or disadvantage, convenient or inconvenient depending on the use.

Mystro256 commented 13 years ago

Perhaps the extensions downloader should be included in master or perhaps installable as a deb package in the PPA (and hopefully official repos) that emesene suggests to install but doesn't depend on it.

ie similar to the python-gtkspell package for emesene in natty-updates: http://packages.ubuntu.com/natty-updates/emesene

c10ud commented 13 years ago

yes, i guess andrea will push it to master as soon as he completes his testing

2011/7/6 Mystro256 reply@reply.github.com:

Perhaps the extensions downloader should be included in master or perhaps installable as a deb package in the PPA (and hopefully official repos) that emesene suggests to install but doesn't depend on it.

ie similar to the python-gtkspell package for emesene in natty-updates: http://packages.ubuntu.com/natty-updates/emesene

Reply to this email directly or view it on GitHub: https://github.com/emesene/emesene-supported-plugins/issues/9#issuecomment-1512026

Mystro256 commented 13 years ago

oh ok, then I'll close this when he does.

Sbte commented 13 years ago

@4ndreaSt4gi ^

Mystro256 commented 13 years ago

I also find this quite effective: https://groups.google.com/forum/#!topic/emesene/-d3OLfhhbOQ

But the extension downloader would make it much easier :)

pepeleproso commented 12 years ago

plugins and themes downloading is now implemented as a build-in feature, so there's no point to keep this open