Laser, Mary wrote:

Folks,

As far as the file with ~ at the end. That's an emacs back up file. I don't know if other editors use a name like that or not. Even if you just opened a file with emacs didn't make any changes, there may still be a backup file.
Hi,
Thanks for the detailed description! I think the instructions are slightly off. You need to create a directory (not a file) in /usr/local/share/fossology/agents/licenses/ for your new template. The directory name should be meaningful. For instance, all Adobe license are under the directory Adobe, like this:
    la...@myhost:/usr/share/fossology/agents/licenses$
    <mailto:la...@myhost:/usr/share/fossology/agents/licenses$> ls -l
    Adobe/
    total 24
    -rw-r--r-- 1 root root 1883 2009-05-08 17:22 Adobe
    -rw-r--r-- 1 root root  599 2009-05-08 17:22 Adobe AFM short
    -rw-r--r-- 1 root root   12 2009-05-08 17:22 Adobe AFM short.meta
    -rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe.meta
    -rw-r--r-- 1 root root  498 2009-05-08 17:22 Adobe short
    -rw-r--r-- 1 root root   84 2009-05-08 17:22 Adobe short.meta

This example contains 3 license templates and their corresponding .meta files. When the license analysis matches text to a template, the license identification is determined by the file name with the closest matching text. Based upon what you describe below, I think you did the right thing - despite the poor instructions! I don't know why the License group shows <Company Name> and <Company Name>~. Did you ever delete the original <Company Name> you added to the license group BEFORE you created a license template? If not, that could be the cause. Please try deleting <Company Name>~. Also, when you get a template match, there should be a "ref" link to click on that displays the reference template used to determine the match. Please try clicking on that and tell me the result. There should be a pathname corresponding to the path where your template lives. Thanks,
Mary
    ------------------------------------------------------------------------
    *From:* [email protected] [mailto:[email protected]]
    *Sent:* Wednesday, June 03, 2009 9:19 AM
    *To:* [email protected]; Laser, Mary
    *Subject:* Re: [FOSSology] FW: Identifying new license in Fossology

    Thank you for your response.  I tried to follow the instructions
    below that were documented to add a license template:

      1.
          Place your file under
          /usr/local/share/fossology/agents/licenses/.
      2.
          Run 'sudo fossinit'. The "..." sequence indicates that the
          licenses are being installed.

    I created a directory under
    /usr/local/share/fossology/agents/licenses/ called <Company
    Name>.  I noticed the files under the other directories containing
    the licenses were not just text files, but a different format.  I
    copied two files from a different directory, it included the file
    that included the license and the .meta file to the directory I
    created.  I then renamed the files to <Company Name> and <Company
    Name>.meta.  I updated the file <Company Name> to contain our
    license.  I then executed the following command:

    /usr/local/bin/fossinit /usr/local/share/fossology/agents/licenses/

    The command completed successfully, but when I went to the "Manage
    License Terms" Page, it showed the Canonical name twice, once as
    <Company Name> and once as <Company Name>~.  I then uploaded a
    file that contained the license and the result was it found a
    license of type license, not <Company Name>.  It seems that I'm
    not creating the license template correctly.  Could someone please
    provide details on how to properly create a license template under
    /usr/local/share/fossology/agents/licenses that has the same file
type as the others.
    Thank You



    --- On *Tue, 6/2/09, Laser, Mary /<[email protected]>/* wrote:


        From: Laser, Mary <[email protected]>
        Subject: [FOSSology] FW: Identifying new license in Fossology
        To: "[email protected]" <[email protected]>
        Date: Tuesday, June 2, 2009, 4:08 PM

        Oops!  forgot to cc the list.
        ------------------------------------------------------------------------
        *From:* Laser, Mary
        *Sent:* Tuesday, June 02, 2009 1:08 PM
        *To:* '[email protected]'
        *Subject:* RE: [FOSSology] Identifying new license in Fossology

        If you are trying to add an entire license vs.. a phrase, you
should follow the directions for adding a license template. License Terms are used to "fine tune" the results of an
        identified license.  For instance, if a GPL v2 license is
        identified as GPL with unknown version, the section of
        identified license text will be compared against License Terms
        to pinpoint the exact license (GPL v2).
From what you've described, the license cannot be identified
        (because there is no template).  Therefore, there is no
        license text to compare against the License Terms.
HTH,
        Mary

            
------------------------------------------------------------------------
            *From:* [email protected]
            [mailto:[email protected]] *On Behalf Of
            *[email protected]
            *Sent:* Tuesday, June 02, 2009 11:52 AM
            *To:* [email protected]
            *Subject:* [FOSSology] Identifying new license in Fossology

            Hello,
I am trying to identify a new license in Fossology. I am
            using the "Manage License Terms" page through the UI to do
            this but am having some difficulty.  I created a new
            Canonical name called "Company Name" and created a new
            term that was specific to that group.  The term was the
            following:  "Copyright Company Name".  I then did
            an Upload from a URL which contained a license file that
            contained that term.  However, the result was it did not
            find the license.  What's strange is when I add the term
            "proprietary" to the group, it recognizes it, but any
            other phrase, it does not recognize.  Should I be using
            the UI to identify a new license or should I follow the
            instructions on the page "How to Add a License Template or
            License Phrase and Re-Analyze Licenses" in the
            documenation to do this?  The documentation says
            it requires re-running the build and modifying the
database. Any help is greatly appreciated. Thanks


--
Mark Donohoe
MOST/OSTT, Cupertino CA.
fossology.org

_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology

Reply via email to