Bob and Mary,
Thank you for kind and very useful responses.
>>>> (1) License Name list
I compared the license list on the FOSSology web site Mary told and parse.c
(and nomos.h), and I've found some difference.
[Licenses not described in the web site]
(1) both FOSSology v.1.4.1 and v.2.0.0RC1
- "GPLv2+KDEupgradeClause"
- "GPL-Bison-exception"
- "Intel-only-FW"
(2) only FOSSology v.2.0.0 rc1
- "WebM"
- "MPL_v2.0"
- "CCA-ND_v3.0"
[Licenses that are not used(perhaps)]
- "Free-SW(run-COMMAND)"
- "GNU-style(interactive)"
These licenses are defined in parse.c and are listed in the web site,
but they are not compiled because of "#if 0" and "#ifdef OLD_VERSION".
>>>> (2) How to detect/assume OSS package(/module/library) names
>>> I am spending some time investigating open source discovery methods
>>> (antelink, joa, open logic, etc) but I've just begun.
That functionality really helps us (and many engineers). We are very
looking forward it.
Best regards,
>This list should be 99% right. It hasn't been maintained for quite a while
>though.
>
>
>On May 17, 2012, at 12:40 PM, Laser, Mary wrote:
>
>> I had a hard time finding the license list, too. Here it is:
>> http://www.fossology.org/projects/fossology/wiki/Nomos_liclist_
>>
>>
>>> -----Original Message-----
>>> From: [email protected] [mailto:fossology-
>>> [email protected]] On Behalf Of Gobeille, Robert
>>> Sent: Thursday, May 17, 2012 11:51 AM
>>> To: Junji Yoshida
>>> Cc: [email protected]
>>> Subject: Re: [FOSSology] Output License Names, and how to extract OSS
>>> package information
>>>
>>> Hello Junji,
>>>
>>> 1) There used to be a list of all the license names on fossology.org
>>> but I don't see it now. Since you know about parse.c, that is probably
>>> the best way to generate a list of names. Start with
>>> grep INTEREST parse.c|sort -u
>>>
>>> When you see a line like:
>>> INTERESTING(lDebug ? "BitTorrent(ref)" : "BitTorrent");
>>>
>>> that means that the signature (in STRINGS.in) named BitTorrent(ref)
>>> will be reported as the BitTorrent license (unless lDebug is turned
>>> on).
>>>
>>> 2) Packages to fossology mean debian and rpm packages. The package
>>> agent will identify these. As you mentioned, we don't have an open
>>> source discovery module. You can create a bucket to list all of these
>>> packages, but it doesn't sound like this is what you are looking for.
>>>
>>> I am spending some time investigating open source discovery methods
>>> (antelink, joa, open logic, etc) but I've just begun.
>>>
>>> Bob Gobeille
>>> [email protected]
>>>
>>>
>>> On May 17, 2012, at 2:10 AM, Junji Yoshida wrote:
>>>
>>>> (1) License Name list
>>>>
>>>> Is there any way to obtain a list of all License Names that
>>>> FOSSology outputs, such as "GPL_v2" and "No_license_found" ?
>>>>
>>>> If I need to see source code(s) such as parse.c or a web page,
>>>> please let me know.
>>>>
>>>>
>>>> (2) How to detect/assume OSS package(/module/library) names
>>>>
>>>> Is there any way to detect or to assume what OSS package(s) are
>>>> included in uploaded file(s) ? For examples, "this file(s) contains
>>>> libjpeg", "this file(s) contains busybox" and so on.
>>>>
>>>> Of course, I understand that FOSSology does not have database of
>>>> existing OSS and that does not compare source codes with those of
>>>> such OSS.
>>>
>>> _______________________________________________
>>> fossology mailing list
>>> [email protected]
>>> http://lists.fossology.org/mailman/listinfo/fossology
>
_______________________________________________
fossology mailing list
[email protected]
http://lists.fossology.org/mailman/listinfo/fossology
