Gianluca Sforna wrote:
Hi Arne,
I raised some questions about the use of your lib, but there were
nothing personal :)
I was worried because I got the impression openwengo has already a
huge number of dependencies and a record for patching upstream
sources, complicating the work for packaging purposes on the various
linux distros.
So I just wanted to be sure they took their time to evaluate all
aspects of the proposal.
Now, I really thank you for the clarifications, they are really appreciated.
I do understand the argument of the increasing number of dependencies. I
try to keep the number dependencies of unicap as low as possible.
Currently unicap only depends on libraw1394 for IEEE-1394 devices ( and
I guess there is no way around that ).
I think currently the main issue is that there are no .deb/.rpm packages
of unicap. That would make dependency tracking a lot easier for
packagers, I guess.
Great. This was my primary concern (and the lack of CVS did not allow
me to check for activity). I would only like to ask you if you are
going to evaluate patches coming from openwengo, for an eventual
inclusion in future releases.
I am evaluating every input that comes from the users ;-) Especially
patches, of course. But any other input is also highly appreciated.
There is indeed one concern about patches: Since unicap can be
relicensed under a commercial license, I need to be the copyright holder
of the code in the library. This is a problem when one sends me a patch
that contains a non-trivial amount of code since the creator of that
patch would have the copyright of this code. In the event of a library
relicensing, I can not relicense the code from such a patch since I do
now own the copyright.
On the other hand, relicensing is required since most projects in the
industrial imaging area where unicap comes from can not be released as
open source. And I do not want to release unicap under a lesser license
than GPL ( mostly because I would not get any funding at all otherwise
but also because I think a lesser license would not be in the spirit of
open source ).
But again: This will not prevent making additions to unicap at all!
Either I will incorporate any required changes by myself or ( in the
worst case ) would fork unicap internally.
/Arne
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
