Hi Raino,

On Jun 4, 2010, at 6:43 AM, <raino.lintula...@elektrobit.com> wrote:

> Hi Bob,
> I'm able to run bucket analysis with bucket type
> 3 (REGEX), but I still have problems to get any results with 
> other bucket types. As you said documentation is not
> finished and it is little bit ambiguous, for example
> should bucket definition file be stored in
> /usr/local/share/fossology/bucket_pool_name directory
> http://fossology.org/task:buckets
> or 
> /usr/local/share/fossology/bucket_pool_pk directory.
> http://fossology.org/buckets

I didn't know I left the old task:buckets link.  I just corrected it, 
http://fossology.org/buckets is correct, its the bucketpool_pk.

> Can you elaborate syntax for bucket file. For example
> if I want to make a bucket which detects all the version
> of GPL licenses then should I put in a bucket file
> GPL
> or
> "GPL"
> or
> 
> GPL
> GPL_v1
> GPL_v2
> GPLv2
> GPL_v3 etc.

In this case, it seems like using a regex "GPL" is all you need.


> I guess in this case bucket_type should be MATCH_ONLY.

If you want to be very explicit on the list, MATCH_ONLY would look like:

GPL
GPL_v1
GPL_v1+
GPL_v2
GPL_v2+
etc


> Then for license conflict example (MATCH_EVERY) which you mentioned 
> is the syntax:
> --bucket file starts--
> GPL and MPL or
> GPL and OSL
> --bucket file ends--
> or
> --bucket file starts--
> "GPL and MPL" or
> "GPL and OSL"
> --bucket file ends--

MATCH_EVERY files are pipe seperated lists, like:

APSL
Apple Public Source License
BSD style | APSL
CopyrightOnly
commercial
GPL | Commercial
GPL | MPL
GPL | OSL


The REGEX_FILE type is in the format:
{kwd} {regex} {operator} {kwd} {regex}
kwd is "license" or "filename"
operator is "and", "or", "not"
The operator and following kwd, regex are optional
For example:

license "[^,]*(GPL_?v3|Affero_v3)[^,]*" and filename binutils
filename realplayer.*
filename ksh and license ATT
license .*-eula

Bob Gobeille
b...@fossology.org
_______________________________________________
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Reply via email to