Opened 19 years ago
Closed 19 years ago
#2638 closed enhancement (fixed)
Central plugins directory
| Reported by: | Owned by: | Alec Thomas | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.10 |
| Component: | general | Version: | devel |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I think a central directory for global plugins in $prefix/share/trac/plugins would make sense - analogue to the central config file in $prefix/share/trac/conf/trac.ini. This would allow central plugin installation without polluting (or requiring write-access to) site-packages.
Attachments (1)
Change History (7)
comment:1 by , 19 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
Oh, sorry I missed that you mentioned "site-packages" above already.
comment:3 by , 19 years ago
Let me elaborate: We try to run our os installs as controled as possible, that means: Only package-managed installs to system-directories. In our case that means rpm packages.
While some trac plugins can be turned into rpms with setuptools, others can't without patching them. It would be acceptable to drop these into an application owned directory like $prefix/share/trac/plugins, but manually installing stuff into site-packages is just asking for trouble with the next upgrade or system migration.
by , 19 years ago
| Attachment: | sitewide-plugins.diff added |
|---|
Patch implementing of site-wide plugins against r3147
comment:4 by , 19 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:5 by , 19 years ago
| Milestone: | → 0.10 |
|---|---|
| Version: | 0.9.3 → devel |
comment:6 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Added in r3371. Plugins in the central directory must be explicitly enabled.
See the documentation for installing plugins for all projects.