Posts tagged Howto

Google Talk Plugin

997 days
by in Howto, Sabayon Linux

Google Blog announced the make a phone call from gmail yesterday.  It’s google so it has to be good right?  Getting it working can be the fun part tho.  There appears to be two ebuilds out there that one can try.  Gentoo Bugzilla 333769 has a 9999 version and cj-overlay has 1.4.1.0 version to try.  If we follow Sabayon wiki article for 3rd Party ebuilds we can get it installed in no time.

As root:

We need to sync with portage and this will take some time to do.  Enjoy a nice spot of tea or something while it runs:

  • emerge –sync

or you can do some needed edits to the /etc/make.conf file, user your favorite editor as root:

  • edit /etc/make.conf
  • add line: PORTDIR_OVERLAY=”${PORTDIR_OVERLAY} /usr/local/portage/”
  • uncomment: ACCEPT_LICENSE=”*”

the License thing isn’t necessary, but while you are there, might as well

Lets make our directory into our local overlay that you just put into the make.conf file:

  • mkdir -p /usr/local/portage/www-plugins/google-talkplugin/

lets change to the directory to keep things simple:

  • cd /usr/local/portage/www-plugins/google-talkplugin/

lets get the file now:

now we need to digest it so we can install it:

  • ebuild google-talkplugin-9999.ebuild digest

Once your emerge –sync is done you can get busy installing, but lets do this the proper way to mix it with entropy system.

  • emerge google-talkplugin -av
  • Calculating dependencies… done!
    [ebuild N ] media-gfx/nvidia-cg-toolkit-2.1.0017 13,410 kB [0]
    [ebuild N ] www-plugins/google-talkplugin-9999 0 kB [1]
    Would you like to merge these packages? [Yes/No] No

We want to select No cause we don’t want portage to install any more than it has to, so lets use entropy to install the deps.

  • equo install media-gfx/nvidia-cg-toolkit

Lets double check now:

  • emerge google-talkplugin -av
  • Calculating dependencies… done!
    [ebuild N ] www-plugins/google-talkplugin-9999 0 kB [1]
    Would you like to merge these packages? [Yes/No] Yes

Now, we can select Yes and soon we see – Recording www-plugins/google-talkplugin in “world” favorites file…   Pretty painless huh?  So now we need to make entropy find it.

  • equo rescue spmsync
    >> Scanning Source Package Manager and Entropy databases for differences…
    >> Differential Scan…Are you ready ? [Yes/No] Yes

Yes we are ready.

  • >> @@ Someone added these packages. They would be added to the system database:
    >> # www-plugins/google-talkplugin-9999
    >> ++ (1/1) >>> Adding www-plugins/google-talkplugin-9999
    >> @@ Database update completed.

Thanks!

Now you may see portage and entropy complaining about some config files needing updating.

  • equo conf update
    Your choice (type a number and press enter): -9

Use -9 to just dump and get rid of them so you will never be bothered by them again.

Open up your browser and see if the plugin is there.  In firefox and chrome use the url and enter in  about:plugins to see and you should hopefully see something like:

  • Google Talk Plugin Video AcceleratorFile: libnpgtpo3dautoplugin.so
    Version:
    Google Talk Plugin Video Accelerator version:0.1.43.3

Now, even tho my browser sees it, google still said I still needed the plugin.  Apparently a known issue and is hitting people.  Well I switched out the ebuild in this how to for the one in cj-overlay 1.4.1.0 version, digested and emerged it and it worked just fine.  I did this on the Sabayon KDE 5.3 x86 version and got it to work with 1.4.1.0 version.  Which one will work for you?  I dunno, the guy that created the 9999 version claims it works on x86_64, but wasn’t sure about x86.  I haven’t had time to try it out on a 64 bit version of Sabayon yet.  So your mileage may vary, but at least this should get you 99.95% there.

So what did we accomplish here.  We used a supported method to install a package that is not yet in entropy.  We safely mixed portage and entropy.  We have a working google talkplugin.  I can’t be for certain when it will be in entropy, probably once they get a stable ebuild, but it’s already been request on the Sabayon Bugzilla for the entropy team to take a look at, so no need to go requesting it.

Happy Chatting!

Sabayon Linux – 3rd Party Software [Howto]

1786 days
by in Howto

You may run into a really nice piece of software and discover that is it not in portage nor in an overlay.  You really want the software and would like the package manager to handle it for easier maintenance.  I stress using the package manager for everything.  It’s just one of those things you don’t question and follow the proper practices.  One of the first things I do is head over to Gentoo’s bugzilla and see if an ebuild has been submitted.  In this scenario I will use Galaxium im software as an example.  I jump over to Gentoo bugzilla and presto, someone has already done up the ebuild.  Now if you’re new to portage you maybe thinking great, but what do I do with these ebuilds.  So than we need to look at the gentoo wiki for a guide on 3rd party ebuilds.  Let me do a quick walk through of this process.  You will need to be root to do this process.  Since Galaxium has two ebuilds, we need to create two directory structures, which are:(Note I edited the ebuilds and resubmitted them to sabayon linux bugzilla so I will be using those one – reason for edit was so I could install it on my 64 bit install.)

In terminal/konsole

  • su and enter your root password
  • # mkdir -p /usr/local/portage/dev-dotnet/libanculus-sharp
  • # mkdir -p /usr/local/portage/net-im/galaxium

    How do you know what to name the directories?  You want to follow the proper categories layout that Gentoo uses.

    First thing we need to do is make sure your /etc/make.conf has the correct line in it so it can find your custom ebuilds.  Simply add PORTDIR_OVERLAY=”/usr/local/portage” to it if it’s not there.

    Than we need to get the ebuilds into the directories and digest them so we can install them, let’s start with libanculus-sharp first:

    • # cd /usr/local/portage/dev-dotnet/libanculus-sharp  << changes u to the correct directory >>
    • # wget -O libanculus-sharp-0.3.1.ebuild http://bugs.sabayonlinux.org/attachment.cgi?id=53 << will get the ebuild and put it in the directory >>
    • # ebuild libanculus-sharp-0.3.1.ebuild digest  << prepares the ebuild for install >>

    You will notice when you digest a file it will retrieve the files from the internet it needs and place them into your /usr/portage/distfiles  Now you can emerge your ebuild by:

    # emerge libanculus-sharp

    Now we can do Galaxium:

    • # cd /usr/local/portage/net-im/galaxium
    • # wget -O galaxium-0.7.3.ebuild http://bugs.sabayonlinux.org/attachment.cgi?id=52
    • # ebuild galaxium-0.7.3.ebuild digest
    • # emerge galaxium

    Pretty painless and now your ebuild is there to stay and it’s easy to maintain when a new version comes out.  Now you maybe thinking what do I do if I can’t find an ebuild for the software I want.  Well you can learn how to make an ebuild or use the sabayonlinux bugzilla and request an ebuild and maybe some kind package maintainer will build it and put it in the overlay for you.  You can request a package for Entropy package manager also.  The above method works great tho if you can’t wait for a package or even an updated version to get into an overlay or portage.

    Go to Top