After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 431833 - When running uninstalled, Tomboy should use uninstalled add-ins, not installed add-ins
When running uninstalled, Tomboy should use uninstalled add-ins, not installe...
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
unspecified
Other All
: Normal enhancement
: 1.4.0
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-20 20:57 UTC by Sandy Armstrong
Modified: 2010-06-26 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use uninstalled plugins (392 bytes, patch)
2007-05-06 20:15 UTC, Stefan Schweizer 		none Details | Review

Description Sandy Armstrong 2007-04-20 20:57:37 UTC 
Tomboy looks for plugins in Defines.SYS_PLUGINS_DIR, which is set during ./configure or ./autogen.sh based on the value of prefix.

This is annoying when you want to run uninstalled (make run) to test out some code, but you are stuck with using the installed plugins instead of the uninstalled code you are trying to test.

This could be fixed by using an environment variable instead of a constant, and updating tomboy.in to set that environment variable differently based on whether you're running installed or uninstalled.  But I don't know if that's the best way to fix it.
Comment 1 Stefan Schweizer 2007-05-06 20:15:52 UTC 
Created attachment 87663 [details] [review]
Use uninstalled plugins

I added TOMBOY_PLUGINS_PATH to the shell script but two plugins are deleted then. Do you know why?

[DEBUG]: Removing old "ExportToHTML.dll" plugin...
[DEBUG]: Removing old "PrintNotes.dll" plugin...
Comment 2 Sandy Armstrong 2007-05-06 20:29:19 UTC 
TOMBOY_PLUGINS_PATH overrides the user plugin folder path (~/.tomboy/Plugins).  The code is still looking in Defines.SYS_PLUGINS_DIR at runtime.

Not sure if this is related to your issue, though.
Comment 3 Stefan Schweizer 2007-05-06 20:46:55 UTC 
(In reply to comment #2)
> TOMBOY_PLUGINS_PATH overrides the user plugin folder path (~/.tomboy/Plugins). 
> The code is still looking in Defines.SYS_PLUGINS_DIR at runtime.
You are right. It worked for me because I had no installed version, so all of the plugins were read from the user plugin folder.
Comment 4 Boyd Timothy 2008-02-26 19:16:43 UTC 
Setting the default assignee and QA Contact to "tomboy-maint@gnome.bugs".
Comment 5 Stefan Schweizer 2008-03-28 17:29:48 UTC 
Is this bug still valid?
Comment 6 Sandy Armstrong 2008-03-29 01:17:20 UTC 
(In reply to comment #5)
> Is this bug still valid?

Yes.
Comment 7 Sandy Armstrong 2009-04-25 15:06:57 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > Is this bug still valid?
> 
> Yes.

To elaborate, this is all still valid, because we still load add-ins according to DEFINES.SYS_ADDINS_DIR.  I believe the Banshee work-around includes a different approach to the .addins file, and putting all assemblies in a common bin directory.
Comment 8 Sandy Armstrong 2010-06-26 14:09:38 UTC 
make run fixed in master