Jeff:

> Thanks for your suggestions to try building from spec-files. I spent the
> last few hours trying to build, but keep running into errors that I don't 
> know how to solve (Solaris newbie). For example, when 
> running[i]/opt/pkgbuild/bin/pkgtool build --download SFEtransmission.spec 
> --autodeps[/i] I get a dependency check failure (for SUNWgtk2, SUNWdbus-glib, 
> SUNWgtk2-devel, and SUNWdbus-glib-devel). I looked for these on OpenSolaris 
> IPS, and couldn't find them (I tried installing gtk2 from Blastwave, but it 
> didn't clear the dependency).

The problem you have is that a number of base libraries were moved to
different package names.  These libraries are on the system, but not
in the packages the transmission spec-file now expects them.

You can solve your problem in two ways:

1) Build the missing dependencies from spec-files, which you can
    retrieve from SVN here:

svn co svn+ssh://anon at svn.opensolaris.org/svn/jds/spec-files/trunk 
spec-files

    I'd recommend updating to the latest SS12 compiler + patches beforem
    building.  You probably first need to uninstall SUNWgnome-base-libs*
    and SUNWdbus-bindings* packages before trying to install the
    dependencies with their new package names.

2) Edit the transmission spec-file and remove the lines that say
    "Requires" and "BuildRequires" for the modules it is complaining
    about.  This is a hacky workaround for the problem, but probably
    easier.

Log messages from pkgtool are in /tmp/(packagename).log which can help
with debugging build issues.

> I know for a Solaris dev this is all a piece of cake, but for someone
> new to Solaris or even *nix in general, this set up is a lot more 
> complicated then just being able to set a repository, run a pkg 
> manager, and have everything (including dependencies) taken care of.

Might be nice if someone wrote a simple GUI that downloaded
spec-files, spec-files-other and SFE from SVN, then showed available
spec-files in a list, and allowed users to easily click on one and
try to build it or uninstall it if previously installed.

Brian

Reply via email to