[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: plugins as separate packages for desktop application
From: |
Tobias Geerinckx-Rice |
Subject: |
Re: plugins as separate packages for desktop application |
Date: |
Mon, 29 Jul 2019 19:53:47 +0200 |
Jack,
Jack Hill 写道:
I think a good way forward would be to work with upstreams to
have
their applications support an APPNAME_PLUGIN_PATH variable and
when
plugins are present in a profile they would augment that
variable.
I agree. Many packages already do this & it jives nicely with our
native-search-paths feature.
Two random lessons from previous experience with (well-meaning)
upstreams:
1. Ensure that it's a search path (in the GNU sense of the word),
a standard colon-separated one if at all possible, not just a
single directory.
2a. Ensure that this environment variable can't be too easily
(=accidentally) masked by a user preference, and
2b. don't use it as a 'default value' to initialise a preference
that will later be saved to disc, because that's how we end up
with weird bugs.
Thanks for taking charge of this,
T G-R
signature.asc
Description: PGP signature