[Pkg-mono-devel] CLI packaging: glue module location?

[Mathieu Malaterre]

Hi Mirco,

  Just an update. libgdcm-cil has been uploaded:

http://packages.debian.org/unstable/libgdcm-cil

On Fri, Apr 10, 2009 at 11:57 AM, Mirco Bauer <meebey at meebey.net> wrote:
<...>
> §3.3.1 Naming says:
> "The package should be named libfoo-cil (without a version in the
> package name) and libraries should not be installed into the GAC but
> only into /usr/lib/packagename.

Ok, we have right now:

$ dpkg -L libgdcm-cil
...
/usr/lib/libgdcm-cil/libgdcm.so
/usr/lib/libgdcm-cil/gdcm_csharp.dll
...

Apparently there is no strong policy for the naming convention of the
actual gluelib: libgdcm.so (there might be a conflict once I start
uploading the gluelib for the java wrapping, but that's a different
story).
How about gdcm_csharp.dll ? Is this something people will be comfortable with ?

> The Mono runtime is not fiddling with the LD_LIBRARY_PATH and thus you
> have to hint the runtime where it can find the gluelib using the DLL
> map that goes along with the assembly (CIL lib).

Do you have a small document explaining how to do this ? I am a C++
dev, and only did the C# wrapping, because users were starting to beg
for a C# layer...

> Is the library you are packaging really API unstable? Unversioned
> (non-GACed) packaging should be only done if really needed.

API is stable, if not then this is a bug.

> 3.1.2 is about the general location of files, while GAC and non-GAC
> libs are overriding that definition in 3.2.1 and 3.3.1.

Again, do you have a document explaining what I need to generate using
gacutil ? so far I only provided gdcm_csharp.dll and libgdcm.so and
people seemed happy with only those.

As a side note, I am now generating the XML documentation (gmcs
/doc:gdcm.xml). Where should this file go ?

Thanks again !

-- 
Mathieu