Detailed Instructions for Installing on openSuse
From Bibus
Instructions for Installing on Suse 10.0
Hi.
I'm the author of the original post quoted here. I'd just like to add that the installation procedure for bibus 1.2.0 is much simpler than that quoted below.
Simply move the tar / zipped bibus file to /usr/local/share and untar it. Rename the resulting directory to "bibus". Open a terminal and as root user run the setup script in the /bibus/Setup directory (follow the prompts). Then you should be able to start bibus using the bibusStart script in the bibus directory from your home account.
I added the icon (/bibus/pixmaps directory) to my desktop and wrote a small shell script to start bibus with a mouse click.
The info posted below is hopefully useful if you have any problems... on with the show!
This is a copy of an email that was used for Suse 10.0 that worked for installing on Fedora 5, but I haven't tested it on Suse 10.0. I assume that it works.
Click here for the Original Post
Note: I copied the post here, so that it wouldn't become a dead link. The following has been edited from the original for grammar, spelling errors, etc. However, the original content has remained constant.
Hi all.
This is for anyone who uses OOo in an academic setting. The reference manager Bibus ( http://bibus-biblio.sourceforge.net/ ) is well integrated into OOo and is a fine (if slightly less functional) substitute for Endnote, Procite etc.
It has a fearsome reputation for tricky installation but I have installed it under Suse 10 and found the installation to be surprisingly simple. Here's how I did it:
Download bibus-1.2.0 Untar, rename resulting directory to "bibus" and move it to /usr/local/share Edit lines 2&3 in bibus/Setup/bibus.sh to point to the program directory of your OOo installation (/usr/lib/ooo-2.0/program in my case).
i.e.
export LD_LIBRARY_PATH=/usr/lib/ooo-2.0/program export PYTHONPATH=/usr/lib/ooo-2.0/program
cd to /usr/lib/ooo-2.0/program and create the following symlink
ln -s /usr/lib/libpython2.4.so.1.0 libpython2.3.so.1.0 ln -s /usr/lib/libpython2.5.so.1.0 (for openSUSE 10.2 and openSUSE 10.3)
As root run setup.py from the terminal
cd /usr/local/share/bibus/Setup su password ********************* python setup.py
you should immediatly get a message telling you that there is a correct wxPython 2.6.1.0 installation Click OK button.
Select the OOo installation you want to use. I used the installation that came with the distrobution (Suse 10) ie I selected /usr/lib/ooo-2.0/program.
If you can still see your terminal window there should be lots of messages scrolling down it.
After a few seconds a message box should pop up telling you that setup is finished and that you can start bibus with the bibusStart.py script. Woot!!!! Press the OK button
Go to the terminal
# exit (if you're still logged in as root) .. (to get back into the bibus directory from bibus/Setup python bibusStart.py
This should begin the "First run wizard" which is also located at the botom of the bibus help menu should you to use it again later.
First follow the instructions to activate OOo to listen for UNO connections. When the OOo (or Staroffice - it works as well!) document opens choose to enable macros if asked.
Press the BIG GREEN BUTTON and close the document.
Press Next in the bibus dialogue box.
I chose to use sqlite for my database, my login name for a database login name and put the database in my home directory (/home/iain/bibus_refs)
Then it was done!
Placed a link to bibus on my desktop using the bibus.png image in bibus/pixmaps as an icon and /usr/local/share/bibus/Setup/bibus.sh as the application path.
Started the application and OOo and lo and behold it "just worked".
I've been using JabRef (fine product but it lacks integration - still that may be addressed in the upcoming ver 2.0 release) and I exported my references from that in Endnote format and imported them into bibus that way. The import wasn't perfect but it'll do to be getting on with!
This is the procedure I used for my laptop but when I re-did it on my home box I found that I didn't need to create the symlink. So it's potentially easier than I've detailed above. One caveat - when I tried the same procedure with a freshly downloaded OOo 2.01 I couldn't get bibus and OOo to speak to each other properly. That held me up for ages!!!
Hope this is helpful to someone.
Cheers
Duff
A little update for Opensuse 10.3
Here is a little update for Opensuse 10.3:
For Opensuse 10.3 with Openoffice 2.3 I found that the paths in bibus.cfg need to be changed like this: oopath = /usr/lib64/ooo-2.0/program and NOT oopath = /usr/lib/ooo-2.0/program
For some reason, in the Open Suse 10.3 distribution there are ooo entries under both /usr/lib AND under /usr/lib64 however, in bibus.cfg the latter has to be set as the correct path! The automatic setup script does NOT set the correct path, even though it recognizes the correct ooo- Installation.


