Hello,
I have read that software like pidin are in a public CVS repository. How
do I get to this repository? (I didn’t see any mention on
http://www.qnx.com).
Regards, Vasili
“William Halchin” <bhalchin@syrres.com> wrote in message
news:d48ti5$bso$1@inn.qnx.com…
Hello,
I have read that software like pidin are in a public CVS repository.
How do I get to this repository? (I didn’t see any mention on
http://www.qnx.com> ).
Regards, Vasili
Mario Charest wrote:
“William Halchin” <> bhalchin@syrres.com> > wrote in message
news:d48ti5$bso$> 1@inn.qnx.com> …Hello,
I have read that software like pidin are in a public CVS repository.
How do I get to this repository? (I didn’t see any mention on
http://www.qnx.com> ).
http://cvs.qnx.com
Regards, Vasili
Some items there, notably “gcc”, are licensed to QNX under the GPL.
Now that QNX 6.3 is shipping with gcc 3.x, the CVS repository should
be updated to match, to avoid GPL non-compliance issues. 'Remember,
if you modify GPL source and redistribute binaries, you must
redistribute the source or face copyright infringement charges.
John Nagle
Team Overbot
John Nagle wrote:
Mario Charest wrote:
“William Halchin” <> bhalchin@syrres.com> > wrote in message
news:d48ti5$bso$> 1@inn.qnx.com> …Hello,
I have read that software like pidin are in a public CVS
repository. How do I get to this repository? (I didn’t see any
mention on > http://www.qnx.com> ).
http://cvs.qnx.com
Regards, Vasili
Some items there, notably “gcc”, are licensed to QNX under the GPL.
Now that QNX 6.3 is shipping with gcc 3.x, the CVS repository should
be updated to match, to avoid GPL non-compliance issues. 'Remember,
if you modify GPL source and redistribute binaries, you must
redistribute the source or face copyright infringement charges.
We must make the source available to anyone we provide the binaries to.
Subtle difference. If we have provided you with binaries, you merely
have to ask and we will give you the source. That being said, we’re
currently working on a better way to distribute source so that people
can more easily obtain up to date versions without having to ask.
cheers,
Kris
John Nagle wrote:
Some items there, notably “gcc”, are licensed to QNX under the GPL.
Now that QNX 6.3 is shipping with gcc 3.x, the CVS repository should
be updated to match, to avoid GPL non-compliance issues. 'Remember,
if you modify GPL source and redistribute binaries, you must
redistribute the source or face copyright infringement charges.
Actually, the GPL says you have to provide it to anyone who asks for it,
using whatever means you feel like. AFAIK we’ve been doing that.
–
Chris Herborth (cherborth@qnx.com)
Never send a monster to do the work of an evil scientist.
Chris Herborth wrote:
John Nagle wrote:
Some items there, notably “gcc”, are licensed to QNX under the GPL.
Now that QNX 6.3 is shipping with gcc 3.x, the CVS repository should
be updated to match, to avoid GPL non-compliance issues. 'Remember,
if you modify GPL source and redistribute binaries, you must
redistribute the source or face copyright infringement charges.
Actually, the GPL says you have to provide it to anyone who asks for it,
using whatever means you feel like. AFAIK we’ve been doing that.
Yes. From the General Public License:
"3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections 1 and
2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your cost of
physically performing source distribution, a complete machine-readable
copy of the corresponding source code, to be distributed under the terms
of Sections 1 and 2 above on a medium customarily used for software
interchange."
One practical reason to do this is that it may get the QNX fixes
backported into the main version. If the QNX versions fork the
source, they get further and further out of date. As
has happened. That’s the real problem. QNX is out of sync
with the mainstream GNU code base. The QNX CVS repository
is four years out of date.
GCC 4.0 came out this week. Most of the QNX world is still
on GCC 2.x, although QNX 6.3 ships with an optional
GCC 3.x version.
If the QNX changes were properly backported into the GNU
mainstream, users could try GCC 4.0 right now.
Just like users of embedded Linux variants can.
John Nagle
Team Overbot