Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Steffen DETTMER" <Steffen.DETTMER@ingenico.com>
To: "Robert Dewar" <dewar@adacore.com>
Cc: "Steffen Dettmer" <steffen.dettmer@googlemail.com>,
	"Everyone" <gdb@sourceware.org>
Subject: Re: generic query regarding GPL and licensing terms associated with gdb
Date: Fri, 27 Aug 2010 11:38:00 -0000	[thread overview]
Message-ID: <20100827113842.GJ6664@elberon.bln.de.ingenico.com> (raw)
In-Reply-To: <4C743A8D.7010101@adacore.com>

* Robert Dewar wrote on Tue, Aug 24, 2010 at 17:33 -0400:
> Steffen Dettmer wrote:
> 
> >As I understood, one of the most essential key points of GPL is
> >exactly that it is not possible to licence code under terms of
> >GPL and redistribute any derived work without offering this
> >derived work also under the terms of the GPL.
> >So I think "take GPL code, modify it [...] and then distribute it
> >without giving a GPL license" simply is not allowed at all.
> 
> But my point was that if you do this (and are thus in a
> position of potential copyright infringement), this act
> does not cause you to lose rights to your trade secrets
> or copyrighted code that may have been distributed at the
> same time.

Thank you for explaining. I think now I see the point.

I assumed that in such a case the source code /must/ be made
available, if the owner rejects that, court would enforce it, as
for example happend with LinkSys WRT.

But of course this was though to short. For example it could not
be that someone includes third-party code which ends up as GPL'd
sources because someone else put it into work derived from GPL'd
product. Also, the violator could buy a different licence from
the copyright holder (which might be given
alternatively/additionally to the GPL).

> If you are judged to have infringed, then you must cure
> the copyright infringement in the future. In the case of
> the GPL, one way you could do this *at your option* is
> to release all your code under the GPL, but you are never
> forced to do this.

Yes, thank you for the explanation.
(so in the example of LinkSys they released the code because the
alternative - not using a firmware on the routers - was no option).

oki,

Steffen

--[ end of message ]----------------------------------------------->8=======













































 
About Ingenico: Ingenico is a leading provider of payment solutions, with over 15 million terminals deployed in more than 125 countries. Its 2,850 employees worldwide support retailers, banks and service providers to optimize and secure their electronic payments solutions, develop their offer of services and increase their point of sales revenue. More information on http://www.ingenico.com/.
 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
 P Please consider the environment before printing this e-mail
 
 


  reply	other threads:[~2010-08-27 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  4:08 paawan oza
2010-08-13  5:04 ` Robert Dewar
2010-08-13  6:16   ` paawan oza
2010-08-13  7:56     ` Martin Schröder
2010-08-13 14:26       ` Robert Dewar
2010-08-13 15:35         ` Martin Schröder
2010-08-13 16:18           ` Robert Dewar
2010-08-13 17:50             ` paawan oza
2010-08-13 18:15             ` Martin Schröder
2010-08-24 21:13               ` Steffen Dettmer
2010-08-24 21:33                 ` Robert Dewar
2010-08-27 11:38                   ` Steffen DETTMER [this message]
2010-08-15 16:40           ` Florian Weimer
2010-08-13 14:24     ` Robert Dewar
2010-08-13 15:50 ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100827113842.GJ6664@elberon.bln.de.ingenico.com \
    --to=steffen.dettmer@ingenico.com \
    --cc=dewar@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=steffen.dettmer@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox