[Mono-dev] Packaging NAnt

Wade Berrier wberrier at novell.com
Fri Jul 21 05:06:28 EDT 2006


On Sat, 2006-07-15 at 14:32 +0200, Mirco Bauer wrote:

> To me this sounds like you try to package binaries, which is bad for
> different reasons. One reason you just found, you can't predict the
> references that will be used.
> If you compile nant correctly from source, you will have the expected
> 1.0.5000.0 refs and your RPM scripts will be happy.

The issue is that the nant source ships binaries that are compiled
against 1.0.3300.0, which is fine because it's important that a program
be able to ship a binary that it has been tested and developed against.

> I discovered the same problem with MonoDevelop, because it ships a
> binary stetic library that was compiled against Gtk# 2.4 but Debian uses
> Gtk# 2.8, so the dependency tracker script cries about references that
> can't be found in the Debian system.

Mike Kestner got around this by using policy assemblies.  He also
updated mono-find-provides for rpm to provide gtk# 2.4 and 2.6 assembly
versions from the gtk# 2.8 rpm.

I ended up having the rpms require >= 1.0.3300.0 as Rafael suggested.

I'm not familiar with debian packaging, but this is how it's been sorted
out with rpm.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060721/7a3ccb60/attachment.bin 

More information about the Mono-devel-list mailing list