[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-librejs] Bundled JS files
From: |
Dura-Kovács , Balázs Marcell |
Subject: |
Re: [Help-librejs] Bundled JS files |
Date: |
Sun, 14 May 2017 23:33:04 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Dear Dmitry,
Thank you for your answer! Yes, it seems a clean way of doing this. I
was hoping that it was possible by placing formated @license comments
inside the minified JS file, but it looks like the referred method is
the only one in this case.
Regards,
Balázs Dura-Kovács
On 2017-05-14 21:12, Dmitry Alexandrov wrote:
>> Dear FSF,
>
> I hope you would pardon me my attepmpt to answer despite I have no
> relationship with FSF.
>
>> Could you please recommend a way of placing license information in a JS
>> file that contains minified versions of multiple free JS libraries that
>> it passes LibreJS? It is a common way to bundle multiple libraries into
>> a single file to minimise the number of HTTP requests and save HTTP
>> overhead.
>
> Does not section 7.1.1 of LibreJs Manual [0] cover that topic?
>
> --8<---------------cut here---------------start------------->8---
> 7.1.1 Specifying multiple licenses for a single JavaScript file
>
> If you compile or concatenate your JavaScript into a single file, the source
> files you’re combining may be released under different licenses. You can
> specify multiple licenses for the file in a JavaScript Web Labels table, like
> this:
>
> <table id="jslicense-labels1">
> <tr>
> <td><a href="all.min.js">all.min.js</a></td>
> <td>
> <a href="http://www.gnu.org/licenses/gpl-3.0.html"
> >GPL-3.0+</a>
> <br />
> <a href="http://www.apache.org/licenses/LICENSE-2.0"
> >Apache-2.0</a>
> </td>
> <td>
> <a href="gpl-script.js">gpl-script.js</a>
> <br />
> <a href="apache-script.js">apache-script.js</a>
> </td>
> </tr>
> </table>
>
> The <br /> tags just make the table more understandable when looking at the
> rendered version of it on the license page. They aren’t required by LibreJS.
>
> If all the licenses contained in the second column are recognized by LibreJS
> to be free licenses, then LibreJS will allow the file in the first column to
> be run.
> --8<---------------cut here---------------end--------------->8---
>
> [0]
> https://www.gnu.org/software/librejs/manual/html_node/Setting-Your-JavaScript-Free.html
>
signature.asc
Description: OpenPGP digital signature