[Pkg-mono-devel] Help on packaging galaxium

David Paleino d.paleino at gmail.com
Thu Jun 19 21:53:29 UTC 2008


On Thu, 19 Jun 2008 23:42:32 +0200, Mirco Bauer wrote:

> On Thu, 2008-06-19 at 10:03 +0200, David Paleino wrote:
> 
> > > dh_clideps
> > > dh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)!
> > > dh_clideps: Warning: Could not resolve moduleref: libmimic for: libmimic-sharp.dll!
> > > dh_clideps: Warning: Could not resolve moduleref: libgalaxium for: Galaxium.GStreamer.dll!
> > > dh_clideps: Warning: Could not resolve moduleref: Iphlpapi.dll for: agsXMPP.dll!
> > > dh_clideps: Warning: Could not resolve moduleref: Kernel32.dll for: agsXMPP.dll!
> > > [..]
> > 
> > Again as before: what to do here?
> 
> There you need some DLLmap love, check the policy chapter about DLL
> maps.

Ok, thanks.

> > Also: the upstream source tarball ships some .dll's:
> > 
> > $ ls -1 dlls/
> > agsXMPP.dll
> > Dependencies.txt
> > Makefile.am
> > Mono.Nat.dll
> > Mono.Nat.license.txt
> > ProxySocket.dll
> > ProxySocket.license.txt
> > $
> > 
> > Debian (and me as well) is usually against using "embedded copies" of code
> > -- I've contacted upstream to have the original sources for those
> > assemblies. Obviously, I will package all those dlls as separate packages
> > (if they aren't already there).
> 
> Debian can live with embedded copies of _source_ _code_

Well, this is opinable too :)
(I believe the security team *will* complain :P)

> but not binaries, they violate the DFSG as you can not change them, nor can
> debian provide security for those. They must be removed from the tarball
> and be replaced with either source or debian library packages.

That's why I made upstream change the tarball.
They already dropped agsXMPP.dll, since it's not yet used, and ProxySocket.dll
has been replaced by the source code (it's a small library, and I doubt anyone
else is using it).
Wrt to Mono.Nat, I'm packaging it (pkg-cli-libs/packages/mono-nat-sharp/) --
and also have a issue about it (if you followed -mentors, you'd understand
:) )

> And be sure to check the licensed of those libraries, I found some
> licensing issues lately in the Mono application area ;)

Yes, I already had a long discussion about licenses with upstream.
I also contacted third parties to check for licenses -- we have no problems
on this side :)

Thanks,
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20080619/64cd0fa2/attachment.pgp 


More information about the Pkg-mono-devel mailing list