Linked by Thom Holwerda on Sat 7th Jan 2006 18:05 UTC, submitted by BSD_User
PC-BSD "PBIs have the advantage of being entirely self-contained. That means casual users won't inadvertently overwrite existing libraries or files by installing and uninstalling applications. This article shows how to create your own PBI, using Digikam as an example of a rather complex package with many library dependencies. While most PBIs will be easier to generate, I want to demonstrate most of the gotchas you may run across when generating your own PBIs." In addition, here is an article explaining how to get MS Office running via WINE on FreeBSD.
Thread beginning with comment 82873
To read all comments associated with this story, please click here.
Pretty cool
by Charles A Landemaine on Sat 7th Jan 2006 20:27 UTC
Charles A Landemaine
Member since:

Dru Lavigne has always written useful articles. Creating PBIs can be very easy when the original package already includes most dependencies. This is the case for most Linux software that you can download from the vendors'web sites.

I noticed a small issue with this tutorial, on p.4:
The name and web site aren't the PBI creator's but the original software developer's name and web site.

Other than that, the MS Office/WINE on FreeBSD/PC-BSD is pretty cool. I think this will be less and less useful as is more and more mature these days. By the way, 2.0.1 is available for PC-BSD too:

But this is a nice hack. I'd like to see IE/WINE for PC-BSD for testing purpose so that I'm sure my web site won't break in IE.

Reply Score: 2

RE: Pretty cool
by molnarcs on Sat 7th Jan 2006 23:23 in reply to "Pretty cool"
molnarcs Member since:

How is built for pc-bsd? I recently switched to ooo-build (2.0.1) which built with the following in pkgtools.conf:

It looks polished and it integrates very well into KDE desktop (crystal icons, desktop themes). Screenshot:

I put up the packages for a friend of mine here, but I'm not sure if they are useful for everyone, because they are athlon-xp optimized (ooo-build itself I think disregards make.conf settings, but the dependencies don't). The directory contains all the dependencies of ooo-build as well (created with pkg_create -R -b ooo-build).

I was always an admirer of pc-bsd and desktkopbsd as well. I think the two projects are not in direct competition, for DesktopBSD seems to be basically FreeBSD with a nice skin and easy installation. It aims at removing the first barrier from installing FreeBSD, but uses ports and default FreeBSD tools. PC-BSD on the other hand aims and desktop users who don't want to dig deeper into the system.

Anyway, I'm quite comfortable with FreeBSD - but I'm not the target audience, I understand that. I have a spare partition for OS review purposes (currently inhabited by Kubuntu) - I may try it out someday ;)

Seeing how KDE centric the project is (which is a good thing IMHO) I was wondering about a tighter cooperation between the KDE project and PC-BSD, afterall, PC-BSD is a good choice for showing off KDE and it's portability, the fact that it runs very well on other unix systems besides Linux. Any thought on that? It might help porting efforts - right now kde@freebsd seems to be a one man show (Michael Nottebrock), but correct me if I'm wrong.

Reply Parent Score: 3