Re: Medical device support for GNUmed
[BTW, Jeff, are you subscribed to Debian Med list? I could spare the CC in
this case.]
On Fri, Jan 07, 2011 at 08:57:57PM -0500, Jeff Buchbinder wrote:
> The "install-deps.sh" script(s) importing the rxtx library could be
> rearranged to import the distribution copy of the jar file for
> packaging purposes.
OK.
> > In these (and a lot of other cases) upstream used parts from other
> > projects, which are in these cases non-free and thus make the packages
> > non-free. My impression from your description of FreeSHIM is that this
> > is the same because you include binary code without source. If you do
> > so you should at least explicitely state (or at least link to a website)
> > the license which clarifies the conditions of usage somehow. The Debian
> > packager needs to check this anyway because ftpmaster is quite picky
> > about this - but IMHO you should mention this in your upstream source
> > as well.
>
> We have the option of just not including the particular driver which
> requires that library, if that's a better alternative. It was broken
> into separate drivers for this sort of purpose. You'll notice that the
> topaz driver is shim-drivers/shim-driver-signature-topaz and can be
> excluded if need be.
If there is a chance to provide separate tarballs freeshim.tar.gz and
freeshim-additional.tar.gz (we can avoid the harsh word 'non-free' to
avoid making afraid users of other distributions which are not as strict
as Debian) this could simplify the Debian packaging if such a split is
possible.
> Unfortunately, as the final product to be
> installed/distributed is a war file, it's a bit more difficult to
> include that "after the fact", although it could be distributed in an
> "exploded" format (as a directory of files rather than the single war
> file) with additional drivers packaged separately.
I admit I'm not that comfortable with this technical details of Java
programs. I'm afraid I need to contact Debian Java list anyway in the
process of packaging.
> I added a LICENSE file which is now in Subversion with the additional
> licensing information, etc.
Cool. Thanks.
Please drop us a not in case you will release a new (minor) version
with your current SVN state. I will now concentrate on the technical
details and will come back (hopefully on Monday evening) with further
details.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: