Difference between revisions of "HOWTO: Installing Bibus in Sabayon Linux - Also how to install sqliteodbc v7.0"
Latest revision as of 22:35, 21 January 2011
Just thought I would write this how to on how to install Bibus in Sabayon Linux using Portato. I am using Sabayon Linux 3.5 Loop 2 without significant modifications. Bibus is available in portage database under apps/text. I ran into some problems when trying to install Bibus so I decided to post this how-to to help newbies do the requiste. I am assuming that you know what portato is but incase you dont just click on the K Menu and type in Portato - it is the GUI for the package manager in Sabayon Linux. Step 1: Fire up Portato and provide the password required. Step 2: Search for Bibus in the bar at the top below the row where File, Emerge, ? is written. Step 3: Bibus will show up under apps/text and on clicking on it you will see the lower bar change. At the time of writing this there will be two entries in the left side under the column which shows versions.Select the latest one (in my case its 1.4.0_rc2) and then click on the button that says "Add to Emerge Queue" However now if you try to install the package using the usual method i.e. Going to the emerge tab and then clicking on the emerge button you will see the installation process will start but will stop after the 1st dependant package Sqliteodbc has been downloaded. The exact text of the error message in my computer goes as follows:
Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> starting parallel fetching pid 23363
>>> Emerging (1 of 2) dev-db/sqliteodbc-0.70 to /
- sqliteodbc-0.70.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
- checking ebuild checksums ;-) ... [ ok ]
- checking auxfile checksums ;-) ... [ ok ]
- checking miscfile checksums ;-) ... [ ok ]
- checking sqliteodbc-0.70.tar.gz ;-) ... [ ok ]
- Please select at least one sqlite library to link against
- The ebuild phase 'setup' has exited unexpectedly. This type of behavior
- is known to be triggered by things such as failed variable assignments
- (bug #190128) or bad substitution errors (bug #200313).
Now obviously this means that sqliteodbc is failing to install due to the error of failure to link against a pre-existing library (to tell you frankly I have no idea what that means!!) Now a quick search in the forum shows that another chap had run into the same problem earlier and the problem of failure of emerge for the aforesaid package fails. This is reported in the Gentoo Bugzilla vide Bug number 162180. The solution for the bug is given at the end of the long post and it basically says that emerge sqliteodbc with the sqlite and sqlite3 use flags.
So back to the process. Go back to search bar and type in sqliteodbc and when the list opens click on the relevant entry. Again you will see the bar open below with the package sqliteodbc and version number 0.7. Beside this you will see another window which has the columns with headers namely enabled, installed , flag and description. Click on the boxes below the enabled column on the rows which say sqlite and sqlite3. Now click on the add to emerge queue button. Portato will report in a window that it is changing the use flags and just click on ok. Next just click on Emerge - this time the package should emerge successfully.
Now just go back to the original bibus package and add that to the emerge queue. Just to be sure I also enabled the flags for sqlite and mysql which enable support for the respective databases and clicked on Add to Emerge Button. Again Portato will bring up that dialog box which says updating use flags. Click on ok. Go to the next tab and click on emerge. Bibus should be emerged properly (Note: I had not tried this but I think that if after enabling the use flags for sqlite and sqlite3 in the sqliteodbc package and then adding bibus and the sqliteodbc package to the emerge queue and emerging them together should also work.)
After the emerge is completed you should have an output which says:
- Byte compiling python modules for python-2.5 .. ... [ ok ]
>>> app-text/bibus-1.4.0_rc2 merged. >>> Recording app-text/bibus in "world" favorites file...
However the problem is that clicking on the bibus entry in the Kmenu doesnot bring up Bibus. The workaround is simple. Just right click on the Bibus entry and choose Edit Item. This in turn will bring up another dialog box in which you can edit the property of the menu entry. Just type in the command /usr/bin/bibus in the relevant box. Here you can also select the icon for the program by clicking on the icon box on the top right and choosing the Bibus Icon from the list. Just search for Bibus and you will get the correct Icon. Leave the rest as same and click on the save button on the top left.
Now another dialog box will tell you it is updating the system menu which is normal. After this is done, clicking on the bibus entry should bring up the bibus window. :-)
I have written this guide intentionally in a long overly simplified format and I apologize if others find this too much. But my target audience is a Linux Newbie who know how to search a forum and does not have too much time in hand to allow him to tinker around.