From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1eAHGv-0004g3-R5 for ptxdist@pengutronix.de; Thu, 02 Nov 2017 16:19:10 +0100 Received: by mail-wm0-x235.google.com with SMTP id r68so12183050wmr.3 for ; Thu, 02 Nov 2017 08:19:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20171102123833.izbaa57v65ktzxwd@pengutronix.de> References: <20171101110105.diihar3apnoooszg@pengutronix.de> <20171102123833.izbaa57v65ktzxwd@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Thu, 2 Nov 2017 16:19:03 +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="===============0280098581==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============0280098581== Content-Type: multipart/alternative; boundary="001a114699dc2bfcb2055d01827b" --001a114699dc2bfcb2055d01827b Content-Type: text/plain; charset="UTF-8" 2017-11-02 13:38 GMT+01:00 Michael Olbrich : > On Thu, Nov 02, 2017 at 01:20:17PM +0100, Guillermo Rodriguez Garcia wrote: > > 2017-11-01 12:01 GMT+01:00 Michael Olbrich : > > > 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? > > No, you need to use collections as well. There is some stuff about this in > the documentation. > Ah, yes. > > > > 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... > > Why? Sysroot is not used for the target rootfs. Do the files conflict with > other packages? In this case, you could define a custom .install.post > target in the package makefile. That's the stage that copies the files to > sysroot-target. > Sorry for the confusion, I think I am mixing the sysroot-target with the target rootfs. The actual question should have been: When I do ptxdist targetinstall , the .ipk will be built, files copied to sysroot etc. If I now recreate the rootfs images (via ptxdist images), will the files from this .ipk (which has now been built) be included? This is what I want to avoid. The reason as you point out is that these files conflict with other packages. Thank you, Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --001a114699dc2bfcb2055d01827b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


2017-11-02 13:38 GMT+01:00 Michael Olbrich <m.olbrich@pengutron= ix.de>:
= On Thu, Nov 02, 2017 at 01:20:17PM +0100, Guillermo = Rodriguez Garcia wrote:
> 2017-11-01 12:01 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > 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 "hot= fix" 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 pla= tform is
> > > rebuilt. Is it possible to have ptxdist build an .ipk packag= e that will
> > not
> > > be included in the filesystem images ?
> > >
> > > I was hoping that marking the package as "M" in pt= xdist 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 bi= t 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 s= omething?

No, you need to use collections as well. There is some stuff about t= his in
the documentation.

Ah, yes.
= =C2=A0

> > If you use the regular images, then you can create a "lazy&q= uot; package.
> > Just create a normal package and then modify the makefile like th= is:
> > "PACKAGES-$(PTXCONF_..." -> "LAZY_PACKAGES-$(PT= XCONF_..."
> >
> > 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= <pkg-name>" to
> > build it.
> >
>
> But then when I do ptxdist targetinstall <pkg-name>, the .ipk wi= ll be
> built, but will the files also be added to sysroot? The latter is what= I
> would like to avoid...

Why? Sysroot is not used for the target rootfs. Do the files conflic= t with
other packages? In this case, you could define a custom <pkg>.install= .post
target in the package makefile. That's the stage that copies the files = to
sysroot-target.

Sorry for the confusion= , I think I am mixing the sysroot-target with the
target rootfs. = The actual question should have been:
=C2=A0
When I do = ptxdist targetinstall <pkg-name>, the .ipk will be=C2=A0built, files<= /div>
copied to sysroot etc.

If I now recreate= the rootfs images (via ptxdist images), will the files from
this= .ipk (which has now been built) be included? This is what I want
to avoid.

The reason as you point out is that the= se files conflict with other packages.

Th= ank you,

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