lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jokin Cuadrado <joki...@gmail.com>
Subject Re: SharpZipLib dependency
Date Mon, 30 Nov 2009 11:03:12 GMT
You can take a look to this thread, but if you use the .net
compression, you will broke the compatibility with java versions.

http://www.mail-archive.com/lucene-net-user@incubator.apache.org/msg00427.html


On Mon, Nov 30, 2009 at 6:08 AM, Ron Grabowski <rongrabowski@yahoo.com> wrote:
> SharpZipLib has always had an exclusion to its normal license if you're just linking
to the .DLL:
>
> http://www.icsharpcode.net/OpenSource/SharpZipLib/
> "Bottom line In plain English this means you can use this library in commercial closed-source
applications."
>
> ICompressionAdapter looks simple enough...could it be implemented using the Framework's
GZipStream?---- Original Message ----
>
> From: George Aroush <george@aroush.net>
> To: lucene-net-dev@incubator.apache.org
> Sent: Sun, November 29, 2009 12:48:57 AM
> Subject: RE: SharpZipLib dependency
>
> Out of the box, Lucene.Net should not have any external dependency. This was
> the case till 2.4; with 2.9.1, I would like to see that old behavior.
>
> My suggestion is this gets fixed by using reflections to load SharpZipLib or
> not, at run time.  This is important because not everyone compiles
> Lucene.Net (think of our VB.NET users) or can use SharpZipLib (think of
> license issue).
>
> -- George
>
>
> -----Original Message-----
> From: Digy [mailto:digydigy@gmail.com]
> Sent: Thursday, November 26, 2009 11:24 AM
> To: lucene-net-dev@incubator.apache.org
> Subject: RE: SharpZipLib dependency
>
> Is is related with Licensing issues.
>
> DIGY.
>
> -----Original Message-----
> From: runenur [mailto:runenur@gmail.com]
> Sent: Thursday, November 26, 2009 10:43 AM
> To: lucene-net-dev@incubator.apache.org
> Subject: SharpZipLib dependency
>
> Hey guys,
>
> I just tried to do a clean compile of the code base, and notices that
> there's a dependency to the SharpZipLib assembly. If this is a
> necessary dependency, why is the assembly not included in the svn
> repository? It is considered best practice to have all dependencies
> checked into the repository, so that it is possible to do a clean
> build by doing a check out, open the solution file, and build. Manual
> steps like downloading a dependency are friction that will scare
> people away.
>
> Best regards,
> Rune
>



-- 
Jokin

Mime
View raw message