Showing my ignorance here, but is a manifest created with all of the packaged
licenses? Is it possible for the developer to ship that if they see fit?
I think what Otavio was trying to do was to keep /lib/firmware from being
cluttered with license files. At least, that is the benefit as I see it.
On 3/24/13 10:42 AM, Otavio Salvador wrote:
On Sun, Mar 24, 2013 at 12:01 PM, Eric Bénard <e...@eukrea.com> wrote:
Hi Otavio,
Le Sat, 23 Mar 2013 17:30:58 -0300,
Otavio Salvador <ota...@ossystems.com.br> a écrit :
We don't ship license files with packages and firmware packages are no
different; drop them.
Signed-off-by: Otavio Salvador <ota...@ossystems.com.br>
there may be a good reason to distribute the license files together with
the firmware's binairies : it's often requested by the firmware's
license.
For example in bcm43xx
2. Restrictions. Licensee shall distribute Software with a copy
of this Agreement.
In this case we'll need to have a -license package for each license as
we often have more than one fw covered by same license. I'd like to
someone to comment on this so I can send a patch to fix it.
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
