[MonoDevelop] recent monodevelop packages?

[Michael Hutchinson]

On Fri, Feb 15, 2008 at 10:11 AM, Travis Staloch <twostepted at yahoo.com> wrote:
<...>
> When I try to build mono-addins with the commands
> $ cd Mono/mono-addins
> $ export PATH=$PATH:/usr/sbin
> $ osc build Fedora_8 i586 *.spec --no-verify
>
> I get the message: ===>
>   ...
>   checking for GTK_SHARP_20... configure: error: Package requirements
> (gtk-sharp-2.0) were not met:
>
>   No package 'gtk-sharp-2.0' found
>
>   Consider adjusting the PKG_CONFIG_PATH environment variable if you
>   installed software in a non-standard prefix.
>
>   Alternatively, you may set the environment variables GTK_SHARP_20_CFLAGS
>   and GTK_SHARP_20_LIBS to avoid the need to call pkg-config.
>   See the pkg-config man page for more details.
>
>   error: Bad exit status from /var/tmp/rpm-tmp.70802 (%build)
>
>
>   RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.70802 (%build)
>
>   The buildroot was: /var/tmp/build-root
> <===
>
> Even though it showed that gtk-sharp2-2.10.0-6.fc8 was installed:
>   ...
>   installing gtk-sharp2-2.10.0-6.fc8
>   installing policycoreutils-2.0.31-7.fc8
>   ...
>
> Any ideas how I should proceed?  Do I need to make adjustments to the
> ./configure file?

Well, that's using the fc8-supplied GTK# rpm, rather than your locally
built one. You could break it open and check that it's installing
gtk-sharp-2.0.pc, and where it's being installed to. It may be that
the "official" Fedora packages split some stuff into a "devel"
package. (It may be easier if you get osc to use your locally-built
GTK# package -- see next comment)

> My goal is to get monodevelop to build eventually and when I try to build it
> with osc, I get this message:
> $ cd Mono/monodevelop
> $ osc build Fedora_8 i586 *.spec --no-verify
> Getting buildinfo from server
> buildinfo is broken... it says:
> expansion error: nothing provides gconf-sharp2, nothing provides
> gtksourceview-sharp2, nothing provides vte-sharp2, nothing provides
> mono-addins

Hm, it could be that the build service won't pick up dependencies from
your local copy of the repository, only from built packages on the
build service. I don't really know much about this, but one fix would
be to request a build service account yourself and copy (or link and
patch) the packages to your home directory. Later, Wade can push your
fixes into the main Mono repo.

-- 
Michael Hutchinson
http://mjhutchinson.com