[aur/jabref] Missing files after installation, incomplete installation

[husten1997]

After the installation of the packages aur/jabref not all files required for the integration with the browser extension are installed. The file /opt/jabref/lib/jabrefHost.py (and the whole folder structure /opt/jabref/) is missing. Further the *.py files requires the executable to be spelled in lowercase (it is spelled JabRef but it should be jabref) for a flawless integration with the JabRef browser extension.

Related Issues: https://github.com/JabRef/JabRef-Browser-Extension/issues/158

[michaellass]

Thanks for bringing this to my attention. This should be relatively easy to fix and I hope to get it done later today. Some notes on this:

• The path /opt/jabref/lib/jabrefHost.py seems to be hardcoded in the browser extension. See https://github.com/JabRef/jabref/blob/master/buildres/linux/native-messaging-host/firefox/org.jabref.jabref.json and https://github.com/JabRef/jabref/blob/master/buildres/linux/native-messaging-host/chromium/org.jabref.jabref.json which are included from https://github.com/JabRef/JabRef-Browser-Extension/blob/master/install_linux.sh.
• Currently we do not install jabrefHost.py at all. We need to do so and it needs to be under /opt/jabref/lib
• A JabRef launch script is expected under /opt/jabref/bin/JabRef. If it's not found, there is a fallback to jabref in the user's $PATH: https://github.com/JabRef/jabref/blob/master/buildres/linux/jabrefHost.py#L17
• That means that we either have to symlink /usr/bin/JabRef to /opt/jabref/bin/JabRef or rename/symlink the script in /bin to jabref

[husten1997]

Thanks for the fast notice.

Because I looked at the other AUR repos (jabref-latest and jabref-git) I thought I could brief you on how jabref-latest handles it: they use the (in fact) hardcoded path in the browser extension for the *.py file (/opt/jabref/lib/jabrefHost.py) and they renamed the script in /usr/bin to lowercase jabref (which jabref yields a result, no symlink to /opt/jabref/bin/jabref used)

[michaellass]

Should be fixed in version 5.1-2 by 0b6db06bd615fd14b3aa4f6f21c4f97f703a46cd. If there are still any problems, please reopen this issue.