themonkeysdidit

OK, it’s not really part 1 as we’ve already bought the shed from B&Q, had it delivered (yes, amazingly they actually turned up this time) and worked out where it’s going to go (in the garden – a bit of a no brainer really). This is the first real work though, digging out the garden where the base is going to go.

We’re going for a concrete base as a fit and forget solution, which means a lot of hard work now, but no work later which sounds pretty good to me. So here it is, one hole (complete with shuttering timber frame in place – thank god it fits!) where some rather pleasant turf used to be.

In fact, I’m so impressed with my digging, here’s another shot from a slightly different angle:

And while we’re at it, check out all the turf I carefully removed:

As you may have guessed, I’m quite impressed with my handy work here! The next step is to compact the ground down, ready for the base layer of stones, it’s exciting this suburban living!

Of course, being slightly geeky, I couldn’t just spend an afternoon digging a hole with no technology to keep me motivated so I set up my camera on the tripod, teathered it to Aperture and created a small automator script to take a picture every 30s. These pictures were then imported into imovie and I created a small time lapse movie and uploaded it to you tube. Isn’t technology great!

Just a quick update to say a gallery has been added. Currently only a selection of pictures from our honeymoon have been uploaded but this should increase over time.

There are plenty of instructions for installing bibblepro on Gentoo using ebuilds, but none that I could find for bibblelite. As such, this is a step by step guide to modifying the bibblepro ebuild to provide a bibblelite ebuild. (If you have no idea what an ebuild is, I’d read up on it a bit first…). Please note, all commands preceded with the ‘%’ character should be run as root, those preceded by the ‘$’ character should be run as a regular user.

Step 1 – Pull in the bibblepro ebuild

Firstly, you’ll need to install layman which provides a set of portage overlays (the bibblepro ebuild is available in one such overlay).

% emerge layman

Next, need to bring in the xwing overlay:

% layman -o http://www.gentoo.org/proj/en/overlays/layman-global.txt
% layman -a xwing

If this the first overlay you’ve pulled in with layman:

% echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf

Finally, check bibblepro is available to install.

emerge --search bibble
Searching...
[ Results for search key : bibble ]
[ Applications found : 1 ]

*  media-gfx/bibblepro-bin [ Masked ]
      Latest version available: 4.10.1
      Latest version installed: [ Not Installed ]
      Size of files: 25,141 kB
      Homepage:      http://www.bibblelabs.com
      Description:   Professional photo workflow and RAW conversion software
      License:       bibblepro

Now we have the layman overlay, we’ll need to create a user overlay and add a modified version of the bibblepro ebuild.

Step 2 – Create a manual overlay

Add the following line “/usr/portage/local/my_overlay” to /usr/portage/local/layman/make.conf so the file now looks like this:

PORTDIR_OVERLAY="
/usr/portage/local/layman/xwing
/usr/portage/local/my_overlay
$PORTDIR_OVERLAY
"

Now add the bibblepro files to our overlay, changing the names so they are now bibblelite:

N.B. The cp command should be typed all on one line

% mkdir -p /usr/portage/local/my_overlay/media-gfx/bibblelite-bin/
% cp -r /usr/portage/local/layman/xwing/media-gfx/bibblepro-bin/bibblepro-bin-4.10.1.ebuild
/usr/portage/local/my_overlay/media-gfx/bibblelite-bin/bibblelite-bin-4.10.1.ebuild

You’ll now have to make some changes to the ebuild file “bibblelite-bin-4.10.1.ebuild” so it builds the lite version, not the pro version. As this file is updated, these instructions will become out of date, but the basic idea is to replace all instances of bibblepro with bibblelite and all instances of BibblePro with BibbleLite.

Now that’s done, you can create the digest:

% ebuild bibblelite-bin-4.10.1.ebuild digest

With any luck it will go and grab the bibblelite binary package from the bibblelabs website and perform some mystical portage voodoo* on it. So long as the voodoo ended without error, we’re good to install!

Step 3 – Install

A quick check to make sure our new package is there:

% emerge --search bibble
Searching...
[ Results for search key : bibble ]
[ Applications found : 2 ]

*  media-gfx/bibblelite-bin [ Masked ]
      Latest version available: 4.10.1
      Latest version installed: [ Not Installed ]
      Size of files: 24,907 kB
      Homepage:      http://www.bibblelabs.com
      Description:   Professional photo workflow and RAW conversion software
      License:       bibblelite

*  media-gfx/bibblepro-bin [ Masked ]
      Latest version available: 4.10.1
      Latest version installed: [ Not Installed ]
      Size of files: 25,141 kB
      Homepage:      http://www.bibblelabs.com
      Description:   Professional photo workflow and RAW conversion software
      License:       bibblepro

Yippee! Let’s install (it’s masked by default so we’ll have to unmask it first)

% echo "media-gfx/bibblelite-bin" >> /etc/portage/package.keywords
% emerge -va bibblelite-bin

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] media-gfx/bibblelite-bin-4.10.1  USE="-andypro -anselpro -cammy -color-popper
-contrast-control -dinkypro -foxypro -ginapro -gradpro -mattypro -ndgrad -percypro -roypro
-sadiepro -shadypro -sharpiepro -siggypro -spectrum -tonypro" 0 kB [1]

Total: 1 package (1 new), Size of downloads: 0 kB
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/portage/local/my_overlay

Would you like to merge these packages? [Yes/No]   Yes

Depending on your system setup and window manager, you might even have a handy icon added to your graphics menu to start bibble with. If not (like me), you should be able to simply start it from the command line (and be immediately presented with an error):

$ bibblelite
bibblelite: error while loading shared libraries: libkodakcms.so: cannot open shared object file:
No such file or directory

We should probably fix that

Step 4 – Troubleshoot

Add the missing library location to the env.d area, regenerate the ld cache and we should be good to go:

% LDPATH=/usr/lib/bibblelabs/bibblelite/libs
% env-update
$ bibblelite
AppPath: /usr/bin
SysHome: /usr/lib/bibblelabs/bibblelite/

Success!

*It’s not really mystical portage voodoo, just recording some checksums and the like.