I did a bit of work on this, and there are now 31 files remaining.
Some of them (see my recent email on unlicensed tools) appear to be
just oversights that will involve tracking down and emailing the
original author. Others just have a header that is
non-standard/malformed and can be easily fixed.
Some of them are more complicated:
- packet-vj.c appears to be illegal for us to use, it seems to include
All Rights Reserved code from Qualcomm.
- packet-ieee80211-radiotap-iter.c is only available under GPL2 (as
opposed to GPL2+, like the rest of Wireshark) so I'm not sure if it is
compatible or not.
- epan/reedsolomon.[ch] appears to be only under the *original* GPL,
so I have no idea.
(I am not a lawyer.)
I am tempted to add the remaining list to the "ignore" set, just so we
start getting emails when new files fail license-check, however I'm
not sure if we'd ever get around to them in that situation...
Thoughts?
On Fri, Sep 6, 2013 at 10:25 AM, Joerg Mayer <jmayer@xxxxxxxxx> wrote:
> Hello,
>
> buildbot is failing in checklicenses - and it looks like the list of
> failed licenses is long. If nobody fixes this, then what's the idea
> behind that check?
>
> http://buildbot.wireshark.org/trunk/builders/Ubuntu-12.04-x64/builds/6101/steps/check licenses/logs/stdio
>
> Ciao
> Jörg
> --
> Joerg Mayer <jmayer@xxxxxxxxx>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe