Re: FHS: Where to store user specific plugins / code

Hi Jonas, On 18-03-09 19:18:50, Jonas Meurer wrote: > Am 09.03.2018 um 14:23 schrieb Georg Faerber: > >> Ian's comments are good for admin-installed plugins that the users can > >> use. In fact there is good precedent for an app checking > >> /usr/lib/pkg/... for plugins installed from Debian pac

Re: FHS: Where to store user specific plugins / code

On 09.03.2018 14:23, Georg Faerber wrote: Hi, > I guess we'll go with /usr/local/lib/schleuder then? Does this sound> like a reasonable choice? That would be my choice. OTOH, it might be nice to have a helper that automatically creates deb packages. (would also be nice for other applications,

Re: FHS: Where to store user specific plugins / code

Am 09.03.2018 um 14:23 schrieb Georg Faerber: >> Ian's comments are good for admin-installed plugins that the users can >> use. In fact there is good precedent for an app checking >> /usr/lib/pkg/... for plugins installed from Debian packages, >> /usr/local/lib/pkg/... for plugins installed by the

Re: FHS: Where to store user specific plugins / code

Hi, On 18-02-28 18:14:17, Marvin Renich wrote: > If a user get to install his/her own plugins, they should go in the > user's home directory, e.g. /home/user/.config/scheduler/plugins/. > Non-root users should not generally be given write permission to > /usr/local, and definitely not to /usr/lib.

Re: FHS: Where to store user specific plugins / code

Hi, On 18-03-01 07:55:08, Peter Silva wrote: > -- it is best practice for daemons/services not to run as root. They > should have an application specific user. Schleuder does use a dedicated user, called schleuder. $HOME is set to /var/lib/schleuder. Inside there mailing list specific data is st

Re: FHS: Where to store user specific plugins / code

Hi all, Thanks for your replies, and sorry for the delay in answering. (Note to myself: Don't write such mails while traveling..) That said, I think I wasn't clear regarding "user specific": On 18-02-28 18:54:14, Georg Faerber wrote: > Currently, we allow users to run / execute their own plugins

Re: FHS: Where to store user specific plugins / code

On Wed, 2018-02-28 at 18:14:17 -0500, Marvin Renich wrote: > * Ian Jackson [180228 17:45]: > > Georg Faerber writes ("FHS: Where to store user specific plugins / code"): > > > Currently, we allow users to run / execute their own plugins, stored in > > > /etc

Re: FHS: Where to store user specific plugins / code

er flag to let users manage their own daemons. On Thu, Mar 1, 2018 at 7:26 AM, Ian Jackson wrote: > Marvin Renich writes ("Re: FHS: Where to store user specific plugins / code"): >> [stuff] > > I agree completely with Marvin's message. > > Ian. >

Re: FHS: Where to store user specific plugins / code

Marvin Renich writes ("Re: FHS: Where to store user specific plugins / code"): > [stuff] I agree completely with Marvin's message. Ian.

Re: FHS: Where to store user specific plugins / code

On Wed, 28 Feb 2018 09:54:14 -0800 Georg Faerber wrote Therefore, I'm wondering what's the correct place: Would /usr/local/lib/schleuder/plugins be sensible? If not, any other place which is more suitable? If they're binaries, the FHS answer is that

Re: FHS: Where to store user specific plugins / code

* Ian Jackson [180228 17:45]: > Georg Faerber writes ("FHS: Where to store user specific plugins / code"): > > I'm maintaining schleuder in Debian [1], a "gpg-enabled mailing list > > manager with resending-capabilities". > > > > Currentl

Re: FHS: Where to store user specific plugins / code

Georg Faerber writes ("FHS: Where to store user specific plugins / code"): > I'm maintaining schleuder in Debian [1], a "gpg-enabled mailing list > manager with resending-capabilities". > > Currently, we allow users to run / execute their own plugins, stored i

FHS: Where to store user specific plugins / code

Hi Debian Developers, all, I'm maintaining schleuder in Debian [1], a "gpg-enabled mailing list manager with resending-capabilities". Currently, we allow users to run / execute their own plugins, stored in /etc/schleuder/plugins. Obviously, that's not the right place, as /etc is for config files,