Bug 245207 – Add support for plugins in >=app-text/jabref-2.4.2

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Christian Faulhammer (RETIRED) 2008-11-01 22:10:14 UTC]

Vlastimil: That's for you, just released

[Comment 1 Vlastimil Babka (Caster) (RETIRED) 2008-11-01 22:16:31 UTC]

You better sleep than make these jokes :) I don't see 2.4.2 on neither homepage nor sourceforge?

[Comment 2 Christian Faulhammer (RETIRED) 2008-11-01 22:18:37 UTC]

http://sourceforge.net/projects/jabref/
http://sourceforge.net/project/platformdownload.php?group_id=92314

Then tell me what I just downloaded...:)

[Comment 3 Vlastimil Babka (Caster) (RETIRED) 2008-11-01 23:17:03 UTC]

Bump is surprisingly trivial for jabref's standards :) but let's wait a bit if we can unbundle the jpfcodegen on this one...

[Comment 4 peyser.alex 2008-11-08 00:10:52 UTC]

Plugins seem to require 2.4.2 to build -- the binaries seem (??) to work, even though they won't compile with 2.4.1, but then they may have a mismatch on what they're distributing. But just bumping the file does pull 2.4.2 in properly.

I've put together ebuilds for the openoffice and emacs integration. I guess I'll attach them here since they depend on 2.4.2.

[Comment 5 peyser.alex 2008-11-08 00:11:37 UTC]

Created attachment 171056 [details]
Ebuild for jabref openoffice integration

[Comment 6 peyser.alex 2008-11-08 00:12:23 UTC]

Created attachment 171058 [details]
Ebuild for jabref emacs integration

[Comment 7 Vlastimil Babka (Caster) (RETIRED) 2008-12-23 12:08:47 UTC]

jabref bumped. as for the plugins, I'm not that sure about packaging them in ebuilds - the OO one is declared alpha quality, the emacs one sounds like something that should be changed (gnuclient -> emacsclient) in the jabref itself to support new emacs? Any insight, fauli?
Generally it would be best if they had plugin manager and people could install them in $HOME/.jabref or something.

[Comment 8 Christian Faulhammer (RETIRED) 2009-01-04 13:03:25 UTC]

(In reply to comment #7)
> jabref bumped. as for the plugins, I'm not that sure about packaging them in
> ebuilds - the OO one is declared alpha quality, the emacs one sounds like
> something that should be changed (gnuclient -> emacsclient) in the jabref
> itself to support new emacs? Any insight, fauli?

 gnuclient is for XEmacs but not GNU Emacs in general.  The behaviour can be introduced for the latter though with app-emacs/gnuserv.

> Generally it would be best if they had plugin manager and people could install
> them in $HOME/.jabref or something.

 Correct.

[Comment 9 Vlastimil Babka (Caster) (RETIRED) 2009-04-23 14:15:15 UTC]

(In reply to comment #8)
> > Generally it would be best if they had plugin manager and people could install
> > them in $HOME/.jabref or something.
> 
>  Correct.
 
So, in 2.5 beta they added plugin manager which lets users install plugins in ~/.jabref/plugins . Is that enough for you? :)

[Comment 10 Christian Faulhammer (RETIRED) 2009-07-09 10:08:33 UTC]

2.5 is in the tree, so we can assume this as fixed.