Summary: | Add support for plugins in >=app-text/jabref-2.4.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christian Faulhammer (RETIRED) <fauli> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | peyser.alex |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Ebuild for jabref openoffice integration
Ebuild for jabref emacs integration |
Description
Christian Faulhammer (RETIRED)
2008-11-01 22:10:14 UTC
You better sleep than make these jokes :) I don't see 2.4.2 on neither homepage nor sourceforge? http://sourceforge.net/projects/jabref/ http://sourceforge.net/project/platformdownload.php?group_id=92314 Then tell me what I just downloaded...:) Bump is surprisingly trivial for jabref's standards :) but let's wait a bit if we can unbundle the jpfcodegen on this one... 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. Created attachment 171056 [details]
Ebuild for jabref openoffice integration
Created attachment 171058 [details]
Ebuild for jabref emacs integration
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. (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. (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? :) 2.5 is in the tree, so we can assume this as fixed. |