Opened 14 years ago
Closed 14 years ago
Last modified 14 years ago
#6524 closed patch (fixed)
Modify MythFrontend Plugin Bundling on OSX
| Reported by: | Owned by: | Nigel | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | Ports - OSX | Version: | unknown |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
OSX bundles support easy configuration of plugins that are placed within the Contents/Plugins directory within the bundle. Performing a "Get Info" operation on the application bundle yields a pane containing a list of all of the plugins present within the Contents/Plugins directory, each with a tick-box allowing it to be easily enabled/disabled.
The osx-packager.pl script places the plugins for MythFronted? in Contents/Resources/lib/mythtv/plugins and therefore cannot take advantage of this functionality. Moving the plugins from Contents/Resources/lib/mythtv/plugins to Contents/Plugins and providing the necessary symbolic links enables the functionality.
Attachments (1)
Change History (11)
Changed 14 years ago by
| Attachment: | bundle_plugins.patch added |
|---|
comment:1 Changed 14 years ago by
| Status: | new → accepted |
|---|
Thanks for the patch, Peter. I wasn't even aware of that 'Get Info' feature.
There are also lots of improvements that should be made to the Created, Version, More Info and Languages sections, if you feel so inclined? e.g. Version should reflect the source SVN revision. The bundle script puts its version in there - that could go into More Info, with the osx-packager version, and maybe the person or org that packaged it? Language could maybe be derived from stuff in Resources/share/mythtv/i18n ?
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
comment:4 Changed 14 years ago by
I initially tried the simpler approach of making Contents/Plugins merely a symbolic link to Contents/Resources/lib/mythtv/plugins but it does not appear to work (on OSX 10.5.6 at least).
It appears to be necessary to do it the way it is done in the patch?
comment:5 Changed 14 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → new |
Do'h. Having Plugins as a symlink lists the plugins and lets you delete them, but not disable or enable them.
comment:6 Changed 14 years ago by
comment:7 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:8 Changed 14 years ago by
20497 gives:
Global symbol "$plug" requires explicit package name at ./osx-packager.pl line 1076. Global symbol "$plug" requires explicit package name at ./osx-packager.pl line 1077. Execution of ./osx-packager.pl aborted due to compilation errors.
The variable $plug is not declared.
The rationale behind the approach I took was that there may be other plug-ins that it may make sense to include in the list but that are not located in the Contents/Resources/lib/mythtv/plugins (for example those in Contents/Resources/lib/mythtv/filters directory).
However, a symbolic link from Contents/Resources/lib/mythtv/plugins to a directory of Contents/Plugins does work.
Patch to move MythFronted? plugins to Contents/Plugins? inside bundle