RFC: Myricom GM message passing system packaging
Hi deb-folks and sorry for the long post.
After a quite long delay in packaging GM message passing system (see my
ITP #114992), I'm going to build up the beast. Some issues I see:
A. Sources include a modified old version of zlib - with the infamous security
bug. Myrinet developers think (?) the bug is not exploitable in GM code.
Probably the best thing to do is to back-port the patch for zlib,
but this could be a pain for future releases... Is there any pointer
to zlib patches? Other suggestions? (Myrinet folks do not mind
excessively security aspects IMHO)
B. Copyright is
<copyright>
**************************************************************************
* *
* Myricom GM networking software and documentation *
* *
* Copyright (c) 1994-2001 by Myricom, Inc. *
* All rights reserved. *
* *
* Permission to use, copy, modify and distribute this software and its *
* documentation in source and binary forms for non-commercial purposes *
* and without fee is hereby granted, provided that the modified software *
* is returned to Myricom, Inc. for redistribution. The above copyright *
* notice must appear in all copies. Both the copyright notice and this *
* permission notice must appear in supporting documentation, and any *
* documentation, advertising materials and other materials related to *
* such distribution and use must acknowledge that the software was *
* developed by Myricom, Inc. The name of Myricom, Inc. may not be used *
* to endorse or promote products derived from this software without *
* specific prior written permission. *
* *
* Myricom, Inc. makes no representations about the suitability of this *
* software for any purpose. *
* *
* THIS FILE IS PROVIDED "AS-IS" WITHOUT WARRANTY OF ANY KIND, WHETHER *
* EXPRESSED OR IMPLIED, INCLUDING THE WARRANTY OF MERCHANTABILITY OR *
* FITNESS FOR A PARTICULAR PURPOSE. MYRICOM, INC. SHALL HAVE NO *
* LIABILITY WITH RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADE *
* SECRETS OR ANY PATENTS BY THIS FILE OR ANY PART THEREOF. *
* *
* In no event will Myricom, Inc. be liable for any lost revenue or *
* profits or other special, indirect and consequential damages, even if *
* Myricom has been advised of the possibility of such damages. *
* *
* Other copyrights might apply to parts of this software and are so *
* noted when applicable. *
* *
* Myricom, Inc. *
* 325 N. Santa Anita Ave. *
* Arcadia, CA 91006 *
* *
**************************************************************************
The "zlib" source is copyright (C) 1995-1996 Jean-loup Gailly and Mark
Adler. See the file "zlib/README" for the copyright notice.
The GM configure scripts were produced by the Gnu Autoconf package and
are redistributed as permitted by that software's documentation,
which states,
There are no restrictions on how the configuration scripts that
Autoconf produces may be distributed or used. [...]
Of the other files that might be used with `configure',
`config.h.in' is under whatever copyright you use for your
`configure.in', since it is derived from that file and from the public
domain file `acconfig.h'. `config.sub' and `config.guess' have an
exception to the GPL when they are used with an Autoconf-generated
`configure' script, which permits you to distribute them under the same
terms as the rest of your package. `install-sh' is from the X
Consortium and is not copyrighted.
</copyright>
So this stuff could be released in non-free, by sending the .deb stuff to
them before. A strange aspect of the story is that their web site require
a password to download all softwares (!). Anyway copyright is apparently
not too restrictive.
C. Building requires some kernel files: both kernel headers and some
post 'make dep' stuff. My best guess is to create a debconf interface
to ask for user's kernel-source and config file in order to run
the correct 'make dep' and possibly create on-fly the right binary deb
file. This is inspired to 'plex86' strategy.
Comments?
--
Francesco P. Lovergine
--
To UNSUBSCRIBE, email to debian-legal-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: