From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from cpsmtpb-ews08.kpnxchange.com ([213.75.39.13]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YLa9g-0006VC-6z for ptxdist@pengutronix.de; Wed, 11 Feb 2015 17:28:48 +0100 Message-ID: <54DB833D.8050604@erwinrol.com> Date: Wed, 11 Feb 2015 17:28:45 +0100 From: Erwin Rol MIME-Version: 1.0 References: <54DB7AD4.5000601@erwinrol.com> In-Reply-To: Subject: Re: [ptxdist] license info Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de The target is the "software", by having the license files on the target the "software" can reproduce the license files when asked (telnet/ssh + cat license.txt) - Erwin On 11-2-2015 17:11, Guillermo Rodriguez Garcia wrote: > In many cases the actual requirement is that the licensing information > is shown in the software itself (e.g. if it has a GUI) or in the > accompanying documentation (e.g. user manuals and such). None of this > would happen automatically if the licenses are just copied to the > target rootfs, so I guess that this would not be very useful in > itself. > > Guillermo > > 2015-02-11 16:52 GMT+01:00 Erwin Rol : >> Hey all, >> >> I see Michael is busy adding license info, which is a good thing. But >> AFAIK (but IANAL) the license info should also be available on the >> target. Does the new ptxdist also install the license files onto the >> target (root)fs ? >> >> - Erwin >> >> -- >> ptxdist mailing list >> ptxdist@pengutronix.de > > > -- ptxdist mailing list ptxdist@pengutronix.de