On Mon, 25 Aug 2008, Bob Friesenhahn wrote:
GPL is often called "copyleft". It is copyrighted code which depends on the
real copyright holder to defend it, but assures the rights (to the source
code) of anyone who receives a binary program based on the work. If the
copyright holders for a wo
On Mon, 25 Aug 2008, Ineiev wrote:
I read the GPL as "we give you the program under the condition that
you shall not distribute it in other way than such and such".
I thought there was no clause "we promise to do this and that".
It is nothing other than getting from the originator
under the term
On 8/22/08, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Fri, 22 Aug 2008, John Calcote wrote:
> >
> > As someone has already mentioned, the rules of the GPL *ONLY* apply to
> > non-originators. The purpose of the GPL is to protect the rights of the
> > originator. The originator of software und
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
> On Fri, 22 Aug 2008, John Calcote wrote:
>>
>> As someone has already mentioned, the rules of the GPL *ONLY* apply to
>> non-originators. The purpose of the GPL is to protect the rights of the
>> originator. The originator of s
Ralf Wildenhues wrote:
> Hello,
>
> * [EMAIL PROTECTED] wrote on Thu, Aug 21, 2008 at 06:07:22PM CEST:
>> >From the very beginning, lies my intention in this point: As there are
>> features to correct and implement, I do not want to have any extra
>> headaches from the svn users like "Oh, i can't
On Fri, 22 Aug 2008, John Calcote wrote:
As someone has already mentioned, the rules of the GPL *ONLY* apply to
non-originators. The purpose of the GPL is to protect the rights of the
originator. The originator of software under GPL has MORE rights than
the GPL grants. He or she has all rights t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yavor Doganov wrote:
> В Fri, 22 Aug 2008 11:21:04 +0800, Tim Post написа:
>
>> The GPL requires only that you make the source code available with all
>> files needed to complete the build. So, in essence, you could exclude
>> the things needed to reb
В Fri, 22 Aug 2008 11:21:04 +0800, Tim Post написа:
> The GPL requires only that you make the source code available with all
> files needed to complete the build. So, in essence, you could exclude
> the things needed to rebuild the build system, but you would alienate
> anyone who is willing to he
Hello,
* Tim Post wrote on Fri, Aug 22, 2008 at 05:21:04AM CEST:
>
> 2 - People updating their svn / git / hg from your's may actually have
> to solve merge conflicts in configure itself, which is a __major__ pain
> in the butt. This happens if they have run 'autoreconf' themselves, or
> similar.
On Thu, 2008-08-21 at 18:07 +0200, [EMAIL PROTECTED] wrote:
> Well till i get things running, i dont want to get anyone fiddle around with
> the build system, that's all. After that, i'd appreciate if anyone comes up
> with a patch, change whatever it is. Help is always welcomed to give
> and take.
On 21-Aug-2008, [EMAIL PROTECTED] wrote:
| >From the very beginning, lies my intention in this point: As there are
| features to correct and implement, I do not want to have any extra
| headaches from the svn users like "Oh, i can't `make install` it here"
| and then i have to troubleshoot that al
Hello,
* [EMAIL PROTECTED] wrote on Thu, Aug 21, 2008 at 06:07:22PM CEST:
>
> >From the very beginning, lies my intention in this point: As there are
> features to correct and implement, I do not want to have any extra
> headaches from the svn users like "Oh, i can't `make install` it here"
> and
First of all many thanks for numerous replies.
- original Nachricht
>
> I have to agree with Bob here. There's only one reason for not
> distributing configure.ac and Makefile.am -- because you're trying to
> keep others from modifying your build system.
>From the very beginning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
> On Thu, 21 Aug 2008, Thomas Dickey wrote:
>>
>> If it's _his_ source code (and assuming that _he_ licensed it GPL), he
>> can distribute whatever set of files he chooses. The restriction
>> applies for files that he gets from
On Thu, 21 Aug 2008, Thomas Dickey wrote:
If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
distribute whatever set of files he chooses. The restriction applies for
files that he gets from someone else.
If no one else is allowed to distribute the package, then what'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 6:51 AM:
>> If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
>> distribute whatever set of files he chooses. The restriction applies for
>> files that he gets from someone else.
>
>
> If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
> distribute whatever set of files he chooses. The restriction applies for
> files that he gets from someone else.
>
yes it's pure my code and i haven't licenced it yet(didn't have time for that).
Having
cleared th
On Thu, 21 Aug 2008, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
> Hello all,
>
> As I couldn't find anything on this specific issue, better ask...
> After being able to compile my code with help of autotools, now i want to
> deliver it as a package. In this cas
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deliver it as a package. In this case I dont want to give out my configure.ac
and Makefile.ams in order to avoid some extra fiddling from others.
20 matches
Mail list logo
