[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: Re: [gnudatalanguage-devel] Fwd: Re: Bug#753620: wishlist: idl/gdl-written software

-------- Original Message --------
Subject: Re: [gnudatalanguage-devel] Fwd: Re: Bug#753620: wishlist: idl/gdl-written software
Date: Fri, 04 Jul 2014 16:57:53 +0200
From: Gilles DUVERT <gilles.duvert@obs.ujf-grenoble.fr>
To: Sylwester Arabas <sarabas@igf.fuw.edu.pl>, 753620@bugs.debian.org
CC: gnudatalanguage-devel@lists.sourceforge.net, GDL Orion Poplawski <orion@cora.nwra.com>

On 07/04/2014 03:25 PM,  Sylwester Arabas wrote:

- how to make these packages usable for IDL / PV-WAVE users?
Since IDL is non-free, I would consider this not as a primary goal. I
would concentrate on GDL.
I wonder what Sywester means by "making useable"...
- should idlastro be splitted into multiple subpackages?
I would split it, if the different parts are somehow usable
independently. Also, not all packages may be usable under GDL (yet), right?
Those are tons of IDL script files. I doubt we can tell if a particular script will fail or not, since it depends on how it is used and the history. I mean, a script that makes nice plots may pass for double precision data, and fail on integer data, a tool using the cursor may crash only when the user clicks where nobodoy ever would have thought clicking possible, etc... Another point is that this idlastro --- which by the way, is the same as "astrolib", no? is a bunch of not-so-well-if-any maintained files, do we want to "support" (read: inherit the problems of) them? My suggestion: we make a small installer-like script that will start at the first use of GDL, that ask for downloading idlastro+coyotelib+mpfit directly from their respective sites (see http://idlastro.gsfc.nasa.gov/). May be do the same for gsshsg data,
as well. No need of handling that at debian level.



Reply to: