Re: GMP's license looks Parrot-compatible

2004-07-01 Thread Andy Dougherty
On Thu, 1 Jul 2004, Leopold Toetsch wrote: No. Please not another library (like ICU), which we have to update in our tree as well. I'd like to just link against it, *if* the library is selected with Configure. Agreed. This reminds me of the situation we faced in perl5 with database libraries. Th

Re: GMP's license looks Parrot-compatible

2004-07-01 Thread Leopold Toetsch
Ion Alexandru Morega <[EMAIL PROTECTED]> wrote: > It would certainly work that way, but there are advantages in including > the source code: > - We could trim down all the functionality we don't use (if there is > any) No. Please not another library (like ICU), which we have to update in our t

Re: GMP's license looks Parrot-compatible

2004-06-30 Thread Scott Bronson
On Wed, 2004-06-30 at 07:15, Dan Sugalski wrote: > In all those cases you've got a binary-only distribution, and a valid > one. (In fact, one that we want to encourage) Section 4, by my reading, > means you've got to ship source to the LGPL component. Well, "provide source" might be a better way o

Re: GMP's license looks Parrot-compatible

2004-06-30 Thread Dan Sugalski
On Tue, 29 Jun 2004, Scott Bronson wrote: > ASSUMPTION > > Parrot will only link to the GMP library, right? Either static or > shared, doesn't matter. > 4: The Parrot project will be distributing source code, not object code, > so this section does not apply. Well... The problem is distributin

Re: GMP's license looks Parrot-compatible

2004-06-30 Thread Ion Alexandru MOREGA
Scott Bronson wrote: On Wed, 2004-06-30 at 00:14, Ion Alexandru Morega wrote: ... there are advantages in including the source code: - GMP's compilation process is aware of the machine's hardware, making optimisations accordingly. It should be compiled along with parrot, for better perfor

Re: GMP's license looks Parrot-compatible

2004-06-30 Thread Scott Bronson
On Wed, 2004-06-30 at 00:14, Ion Alexandru Morega wrote: > ... there are advantages in including > the source code: > - We could trim down all the functionality we don't use (if there is > any) On modern architectures, I don't think that this will actually buy very much. Shared libraries ar

Re: GMP's license looks Parrot-compatible

2004-06-30 Thread Ion Alexandru Morega
I haven't read the LGPL carefully, but there is one point i'd like to make. Scott Bronson wrote: ASSUMPTION Parrot will only link to the GMP library, right? Either static or shared, doesn't matter. It would certainly work that way, but there are advantages in including the source code: - We co