HOWTO: Install Miro 2.0.3 before it finds its way into Entropy

From Sabayon Wiki
Jump to: navigation, search

Ok so I got sick of Miro 1.2.4 not working anymore and wanted to try the new Miro 2.0.3

It actually emerged without much difficulty.

Machine State Prior to Install

Here's my setup. I run a fully updated x86-64 entropy install (so all binary) with 2.6.29-sabayon kernel with kde4.2.

What You Will Need to Accomplish This:

For this you will need:

 
1.  A recently synced portage tree, 
2. The latest miro ebuild here: [http://bugs.gentoo.org/attachment.cgi?id=187487 Gentoo Bugzilla Ebuild]
3. A custom layman repository, or know how to create one
4. A decent working knowledge of how to create a custom local repo 
    (so be able to set up something in /usr/portage/local/layman with proper portage tree structure)
Question.png
Ok, I realize that there are many better ways to modify the files, create the directories, and patch the ebuild than what I do here. These are my technical limitations as I don't have the time right now to learn things like sed, create a patch to an ebuild, and modify DEPENDS in an ebuild, so forgive me if this is longer and more complicated than it really needs to be. You are free to fix this up (it is a wiki afterall) and make it less awkward.

Ok, let's get started:

First do a

 equo update && equo world 

Now we will

 emerge --sync 

Download the ebuild and save it somewhere you will remember.


Create A Custom Repository

Ok now create our custom repo

First make our directories

 mkdir /usr/portage/local/layman/customebuilds

cd into that directory

 cd /usr/portage/local/layman/customebuilds

continue making directories

mkdir media-tv/
cd media-tv/
mkdir miro 

Ok lets put the ebuild into our new directory

 cp /whereever/miro-2.0.3-r1.ebuild /usr/portage/local/layman/customebuilds/media-tv/miro


Question.png
I realize that now portage wants reponames and it will complain, but honestly I don't care to give my custom repos reponames as I am not sharing them out and things will compile regardless. Feel free to add a reponame if it gives you a warmfuzzy.

Ok now update your make.conf

nano /usr/portage/local/layman/make.conf

add a line for /usr/portage/local/layman/customebuilds

File: /usr/portage/local/layman/make.conf
PORTDIR_OVERLAY="
/usr/portage/local/layman/sabayon
/usr/portage/local/layman/customebuilds
$PORTDIR_OVERLAY
"


alright, now we need to pull the ebuild digest

cd /usr/portage/local/layman/customebuilds/media-tv/miro

pull the digest

ebuild miro-2.0.3-r1.ebuild digest


Ok now we will need to clean up some GNOME typos and assorted other issues.

First,

nano /usr/lib/pkgconfig/pm-utils.pc

you need to change

pm_powerhooks=${pm_libdir)/power.d to pm_powerhooks=${pm_libdir}/power.d

It will look like

File: /usr/lib/pkgconfig/pm-utils.pc
prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib64
sysconfdir=/etc

pm_libdir=${libdir}/pm-utils
pm_sysconfdir=${sysconfdir}/pm
pm_sleephooks=${pm_libdir}/sleep.d
pm_powerhooks=${pm_libdir}/power.d
pm_sleepmodules=${pm_libdir}/module.d

save and close

NOTE: It's difficult to see there, but you need to change the end parenthesis ")" to an end parend "}".

Next we need to install a build dependency that is not pulled in by the ebuild.

equo install dri2proto


Now the fun part

emerge -av miro


use ask to make sure you got your ebuild ready to compile and if it's right, let er rip!

Should compile fine now and run like a charm.