it's worse than that. Even if we release source, we can't use GPL'd code
(like gsl) unless we release under the GPL license, which we can't.
On Mon, 1 May 2006, Darren Weber
wrote:
--[PinePGP]--[begin]--
--[PinePGP]-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suppose you could use LGPL code, but something really useful like the
GSL is out of your reach, so long as you will not release source code.
I'm not sure about the R project library, as it may incorporate GSL too;
see
http://www.gnu.org/software/gs
EMAIL PROTECTED] On Behalf Of Bruce
Fischl
Sent: Monday, May 01, 2006 1:02 PM
To: Nick Schmansky
Cc: [EMAIL PROTECTED]; Freesurfer Mailing List
Subject: Re: [Freesurfer] GNU GPL source?
p.s. we can't use GPL because of various MGH restrictions (which also
unfortunately means we can't use any
: Nick Schmansky
Cc: [EMAIL PROTECTED]; Freesurfer Mailing List
Subject: Re: [Freesurfer] GNU GPL source?
p.s. we can't use GPL because of various MGH restrictions (which also
unfortunately means we can't use any other GPL code). We could
conceivably
post an incomplete (and thus u
p.s. we can't use GPL because of various MGH restrictions (which also
unfortunately means we can't use any other GPL code). We could conceivably
post an incomplete (and thus unbuildable version) - would that be helpful?
We're working towards a make/configure type open source, but aren't there
Darren,
The freesurfer source code is not ready to be posted for download just
yet. We are currently replacing some code that we cannot distribute as
open-source.
About your problem with libtiff, I suppose a hacky solution is to try
symlinking libtiff.so.3 to libtiff.so.4. I'll also check if we
