From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm0-x22e.google.com ([2a00:1450:400c:c09::22e]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1eAHlW-0001yj-86 for ptxdist@pengutronix.de; Thu, 02 Nov 2017 16:50:46 +0100 Received: by mail-wm0-x22e.google.com with SMTP id s66so11984952wmf.5 for ; Thu, 02 Nov 2017 08:50:46 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20171102153335.23xsmv63pqlytedw@pengutronix.de> References: <20171101110105.diihar3apnoooszg@pengutronix.de> <20171102123833.izbaa57v65ktzxwd@pengutronix.de> <20171102153335.23xsmv63pqlytedw@pengutronix.de> From: Guillermo Rodriguez Garcia Date: Thu, 2 Nov 2017 16:50:39 +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="===============0383025061==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: "ptxdist@pengutronix.de" --===============0383025061== Content-Type: multipart/alternative; boundary="089e082fe40435599e055d01f354" --089e082fe40435599e055d01f354 Content-Type: text/plain; charset="UTF-8" Hi, 2017-11-02 16:33 GMT+01:00 Michael Olbrich : > On Thu, Nov 02, 2017 at 04:19:03PM +0100, Guillermo Rodriguez Garcia wrote: > > 2017-11-02 13:38 GMT+01:00 Michael Olbrich : > > > > > 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. > > That's what lazy packages are for. The rootfs images are created from the > ipkgs. All lazy packages are excluded from the default package list, so > those wont be included in the rootfs images. > Then this is exactly what I am looking for. Thank you! Guillermo --089e082fe40435599e055d01f354 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,<= /div>

2017-1= 1-02 16:33 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de&= gt;:
On Thu, Nov = 02, 2017 at 04:19:03PM +0100, Guillermo Rodriguez Garcia wrote:
> 2017-11-02 13:38 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > > > If you use the regular im= ages, then you can create a "lazy" package.
> > > > Just create a normal package and then modify the makefi= le like this:
> > > > "PACKAGES-$(PTXCONF_..." -> "LAZY_PAC= KAGES-$(PTXCONF_..."
> > > >
> > > > The package will not be added to the rootfs, however, i= t will not be
> > built
> > > > by default either. So you need to run "ptxdist tar= getinstall
> > <pkg-name>" to
> > > > build it.
> > > >
> > >
> > > But then when I do ptxdist targetinstall <pkg-name>, t= he .ipk will be
> > > built, but will the files also be added to sysroot? The latt= er is what I
> > > would like to avoid...
> >
> > Why? Sysroot is not used for the target rootfs. Do the files conf= lict with
> > other packages? In this case, you could define a custom <pkg&g= t;.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 t= he
> target rootfs. The actual question should have been:
>
> When I do ptxdist targetinstall <pkg-name>, the .ipk will be bui= lt, files
> copied to sysroot etc.
>
> If I now recreate the rootfs images (via ptxdist images), will the fil= es
> from
> this .ipk (which has now been built) be included? This is what I want<= br> > to avoid.
>
> The reason as you point out is that these files conflict with other > packages.

That's what lazy packages are for. The rootfs images are cr= eated from the
ipkgs. All lazy packages are excluded from the default package list, so
those wont be included in the rootfs images.

Then this is exactly what I am looking for. Thank you!

=
Guillermo
--089e082fe40435599e055d01f354-- --===============0383025061== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0383025061==--