From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1eAETw-0008ON-4p for ptxdist@pengutronix.de; Thu, 02 Nov 2017 13:20:24 +0100 Received: by mail-wm0-x232.google.com with SMTP id r196so10683413wmf.2 for ; Thu, 02 Nov 2017 05:20:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20171101110105.diihar3apnoooszg@pengutronix.de> References: <20171101110105.diihar3apnoooszg@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Thu, 2 Nov 2017 13:20:17 +0100 Message-ID: Subject: Re: [ptxdist] How to create "hotfix" packages List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0170589587==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============0170589587== Content-Type: multipart/alternative; boundary="001a114bd80eddc85c055cff020a" --001a114bd80eddc85c055cff020a Content-Type: text/plain; charset="UTF-8" Hello Michael, 2017-11-01 12:01 GMT+01:00 Michael Olbrich : > Hi, > > On Tue, Oct 31, 2017 at 06:28:14PM +0100, Guillermo Rodriguez Garcia wrote: > > For a ptxdist BSP I am managing I need to create a "hotfix" package to > > patch a number of files on already deployed devices. > > > > This package will only be used on devices which are already deployed, and > > its files should not be part of the rootfs images if the platform is > > rebuilt. Is it possible to have ptxdist build an .ipk package that will > not > > be included in the filesystem images ? > > > > I was hoping that marking the package as "M" in ptxdist menuconfig would > do > > the trick :) but that doesn't do what I thought. > > It can be used like that, but for a single package, it's a bit complex. > Do you marking the package as "M"? I tried that but it seems to do exactly the same as when I just enable it (with "*"). Am I missing something? > If you use the regular images, then you can create a "lazy" package. > Just create a normal package and then modify the makefile like this: > "PACKAGES-$(PTXCONF_..." -> "LAZY_PACKAGES-$(PTXCONF_..." > > The package will not be added to the rootfs, however, it will not be built > by default either. So you need to run "ptxdist targetinstall " to > build it. > But then when I do ptxdist targetinstall , the .ipk will be built, but will the files also be added to sysroot? The latter is what I would like to avoid... Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a114bd80eddc85c055cff020a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Michael,

2017-11-01 12:01 GMT+01:00 Michael Olbrich = <m.olbrich= @pengutronix.de>:
Hi,

On Tue, Oct 31, 2017 at 06:28:14PM +0100, Guillermo Rodriguez Garcia wrote:=
> For a ptxdist BSP I am managing I need to create a "hotfix" = package to
> patch a number of files on already deployed devices.
>
> This package will only be used on devices which are already deployed, = and
> its files should not be part of the rootfs images if the platform is > rebuilt. Is it possible to have ptxdist build an .ipk package that wil= l not
> be included in the filesystem images ?
>
> I was hoping that marking the package as "M" in ptxdist menu= config would do
> the trick :) but that doesn't do what I thought.

It can be used like that, but for a single package, it's a bit c= omplex.

Do you marking the package as &= quot;M"? I tried that but it seems to do exactly the same as when I ju= st enable it (with "*"). Am I missing something?
=C2=A0=
If you use the regular images, then you can create a "lazy" packa= ge.
Just create a normal package and then modify the makefile like this:
"PACKAGES-$(PTXCONF_..." -> "LAZY_PACKAGES-$(PTXCONF_...&= quot;

The package will not be added to the rootfs, however, it will not be built<= br> by default either. So you need to run "ptxdist targetinstall <pkg-n= ame>" to
build it.

But then when I do ptxdist ta= rgetinstall <pkg-name>, the .ipk will be built, but will the files al= so be added to sysroot? The latter is what I would like to avoid...


Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com<= /div>
--001a114bd80eddc85c055cff020a-- --===============0170589587== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0170589587==--