Displaying 20 results from an estimated 3000 matches similar to: "Samba 3.0.37 license confusion"
2007 Jul 09
1
Samba Adopts GPLv3 for Future Releases
Samba adopts GPLv3 for future releases.
---------------------------------------
After internal consideration in the Samba Team we have decided to adopt the
GPLv3 and LGPLv3 licences for all future releases of Samba.
The GPLv3 is the updated version of the GPLv2 license under which Samba is
currently distributed. It has been updated to improve compatibility with other
licenses and to make it
2007 Jul 09
1
Samba Adopts GPLv3 for Future Releases
Samba adopts GPLv3 for future releases.
---------------------------------------
After internal consideration in the Samba Team we have decided to adopt the
GPLv3 and LGPLv3 licences for all future releases of Samba.
The GPLv3 is the updated version of the GPLv2 license under which Samba is
currently distributed. It has been updated to improve compatibility with other
licenses and to make it
2014 May 21
1
Linking libsmbclient with GPLv2 Code
Hello everyone,
I'm not sure who to ask about this, but I have a licensing question.
I'm writing a utility to allow Git to connect to SMB shares, which
uses libsmbclient. I was thinking about using libgit2 in my program:
http://libgit2.github.com/ . This library is licensed as GPLv2 only,
with a linking exception to link to any program without restriction.
My understanding is that, since
2015 Oct 19
8
RFC: Improving license & patent issues in the LLVM community
On 19 October 2015 at 18:12, David Chisnall via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> One worry is that Apache 2 is incompatible with GPLv2 (is it incompatible with other licenses?)
This is interesting, I did not know that...
http://www.apache.org/licenses/GPL-compatibility.html
"Despite our best efforts, the FSF has never considered the Apache
License to be compatible
2015 Oct 29
4
RFC: Improving license & patent issues in the LLVM community
On 29 October 2015 at 10:25, Jonas Maebe via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Hi,
>
> Regarding the previously voiced concerns of incompatibilities between the
> Apache and GPLv2 license, I'd like to add one more thing.
>
> I work on a, at this time mostly LLVM-unrelated [1], "GPLv2 or later"
> licensed compiler: the Free Pascal Compiler. Some
2015 Oct 20
4
RFC: Improving license & patent issues in the LLVM community
On Tue, Oct 20, 2015 at 8:59 AM, Rafael EspĂndola
<llvm-dev at lists.llvm.org> wrote:
> On 19 October 2015 at 13:57, Renato Golin via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> On 19 October 2015 at 18:12, David Chisnall via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>>> One worry is that Apache 2 is incompatible with GPLv2 (is it
2007 Jul 24
2
licensing requirements for using the SWIG bindings
Hi,
I'm confused about my licensing obligation with respect to the Xapian
SWIG bindings.
I've got a python wrapper that sits above the standard Xapian
Python/SWIG bindings, and I wasn't sure if the *intent* of the Xapian
team is that my python wrapper - and any code that also uses my
wrapper also falls under GPLv2.
It seems unclear if the FSF's position on dynamic linking in
2016 Mar 12
1
The sad state of samba 4 adaption for home/small business routers.
On 12/03/16 16:08, Jeremy Allison wrote:
> On Sat, Mar 12, 2016 at 12:50:50PM +0100, Luca Olivetti wrote:
>> El 12/03/16 a les 12:37, Rowland penny ha escrit:
>>
>>> Well yes, but these are usually a mass market product and will no doubt,
>>> in the fullness of time, get to use a version of Samba 4 seeing as how
>>> 3.6 has been EOL since March 2015.
2008 Apr 25
3
[ANNOUNCE] Samba 3.2.0pre3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release Announcements
=====================
This is the third preview release of Samba 3.2.0. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Please be aware that Samba is now distributed under the version 3
of
2008 Apr 25
3
[ANNOUNCE] Samba 3.2.0pre3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Release Announcements
=====================
This is the third preview release of Samba 3.2.0. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Please be aware that Samba is now distributed under the version 3
of
2019 Jul 26
3
Revisiting the PHP binding license issues
Hello,
I would like to see Xapian used more widely in the PHP community. The major
obstacle is that binaries of the PHP extension cannot be distributed. I've
been reading earlier discussions on this and wonder if there's now an
option.
My starting points were
https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package and the
discussion at https://trac.xapian.org/ticket/191.
One comment
2008 Jun 10
4
[ANNOUNCE] Samba 3.2.0rc2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=================================
Release Notes for Samba 3.2.0rc2
June 10, 2008
=================================
This is the second release candidate of Samba 3.2.0. This is *not*
intended for production environments and is designed for testing
purposes only.
2008 Jun 10
4
[ANNOUNCE] Samba 3.2.0rc2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=================================
Release Notes for Samba 3.2.0rc2
June 10, 2008
=================================
This is the second release candidate of Samba 3.2.0. This is *not*
intended for production environments and is designed for testing
purposes only.
2008 May 23
4
[ANNOUNCE] Samba 3.2.0rc1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Preamble:
Please help us testing this release candidate! If there are no major
catastrophes, it will become the first major release of Samba 3.2.0.
It might take a few hours until the files will be spread to all mirrors.
=================================
Release Notes for Samba 3.2.0rc1
2008 May 23
4
[ANNOUNCE] Samba 3.2.0rc1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Preamble:
Please help us testing this release candidate! If there are no major
catastrophes, it will become the first major release of Samba 3.2.0.
It might take a few hours until the files will be spread to all mirrors.
=================================
Release Notes for Samba 3.2.0rc1
2009 Dec 27
1
testhelp/maketree.py is GPLv2
Hi,
I have a licensing question:
I'm curious if the fact maketree.py is GPLv2 causes any trouble for
the rest of rsync (which is GPLv3 or later).
--
yours,
Julius Davies
250-592-2284 (Home)
250-893-4579 (Mobile)
http://juliusdavies.ca/logging.html
2010 Nov 30
1
Consistency regarding compiled Cortado 0.6.0 sourceand the official binary
It should probably not be necessary in my case to compile a custom version of the Cortado applet-the official binary works fine, and may be advantageous over a locally-compiled version (regarding compatibility with 1.1-era JVMs), as was mentioned in a previous message. My interest was to include the corresponding source code when distributing the official binary (i.e. as would be required for
2008 Jul 01
13
[ANNOUNCE] Samba 3.2.0 Available for Download
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
==============================================================
"Patience is the companion of wisdom."
Saint Augustine
==============================================================
Release Announcements
=====================
This is the first stable release of Samba 3.2.0.
Please be aware that Samba is now distributed under
2008 Jul 01
13
[ANNOUNCE] Samba 3.2.0 Available for Download
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
==============================================================
"Patience is the companion of wisdom."
Saint Augustine
==============================================================
Release Announcements
=====================
This is the first stable release of Samba 3.2.0.
Please be aware that Samba is now distributed under
2013 Jul 10
2
Help Samba license
Hi,
I want to use library of samba that license is "GPLv2" in my program that is proprietary.
The source code version of samba is 3.0.6.
Is it possible to modify the license to "LGPL"?
Thanks.