I've used the origional rx-lib products in the past. I personally like them, but I cannot "sell" them to my management with this license. I'm curious why this library is moving in this direction.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The library is moving to GPL because we believe it be the best direction for the continued development of the library.
There will be a number of official released by SGB Software which will be supported by ourselves and other members of the project.
Making the library GPL also enables us to use component and source code provided by other developers. Any code submitted to the project will also fall under this licence scheme.
Although the licence will be GPL, there will be a number of ammedments that are currently being looked at by the source forge team.
I will post more information when its available.
Regards
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem is, that GPL is not suitable licence for library. It means, that any application that uses new rxlib must be under GPL. If you would use LGPL you would at least allow dynamic linking - and I think that packages would qualify for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As i said in my previous message, there are a couple of ammendments currently being looked at by the source forge team and we are awaiting approval of these.
If approval is not granted then LGPL is another serious option we can consider.
Kindest Regards
Scott
www.sgbsoftware.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ive considering the LGPL model will take advantages to developers who sells solutions in software that the source is sold separated as a option to customer.
Thanks to All
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've used the origional rx-lib products in the past. I personally like them, but I cannot "sell" them to my management with this license. I'm curious why this library is moving in this direction.
Hello,
The library is moving to GPL because we believe it be the best direction for the continued development of the library.
There will be a number of official released by SGB Software which will be supported by ourselves and other members of the project.
Making the library GPL also enables us to use component and source code provided by other developers. Any code submitted to the project will also fall under this licence scheme.
Although the licence will be GPL, there will be a number of ammedments that are currently being looked at by the source forge team.
I will post more information when its available.
Regards
Scott
The problem is, that GPL is not suitable licence for library. It means, that any application that uses new rxlib must be under GPL. If you would use LGPL you would at least allow dynamic linking - and I think that packages would qualify for that.
Hello,
As i said in my previous message, there are a couple of ammendments currently being looked at by the source forge team and we are awaiting approval of these.
If approval is not granted then LGPL is another serious option we can consider.
Kindest Regards
Scott
www.sgbsoftware.com
Ive considering the LGPL model will take advantages to developers who sells solutions in software that the source is sold separated as a option to customer.
Thanks to All