Re: [Firebird-net-provider] Zlib library

> There is also ILMerge option to include dependency in a package. Somebody would probably need to study the license, whether that's allowed. Also hiding it is nice, but giving "some credits" isn't a bad thing either (and I don't mean some line in README). -- Mgr. Jiří Činčura Independent IT

Re: [Firebird-net-provider] Zlib library

> SharpZipLib looks to be more actively maintained and with clearer and > more > permissive licensing. It's a dependency of most of my project anyway so I > would not mind it. Kind of. On the other hand when it's done, like *done*, there's not much to change. > An alternative to an external

Re: [Firebird-net-provider] Zlib library

One thing I realized now. We might also consider is future .NET Core/CoreCLR support... -- Mgr. Jiří Činčura Independent IT Specialist -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA

Re: [Firebird-net-provider] Zlib library

SharpZipLib looks to be more actively maintained and with clearer and more permissive licensing. It's a dependency of most of my project anyway so I would not mind it. An alternative to an external dependency is an intree copy with unnecesary bits(eg. bzip2,tar) removed. Out of curiosity why is

Re: [Firebird-net-provider] Zlib library

There is also ILMerge option to include dependency in a package. On 21 June 2016 at 11:02, Gerdus van Zyl wrote: > SharpZipLib looks to be more actively maintained and with clearer and more > permissive licensing. It's a dependency of most of my project anyway so I >