mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to create "hotfix" packages
Date: Thu, 2 Nov 2017 16:33:35 +0100	[thread overview]
Message-ID: <20171102153335.23xsmv63pqlytedw@pengutronix.de> (raw)
In-Reply-To: <CABDcavbDrum-N-PpxGHShXJ+FenPFbL4qsLgv73jg0z0HJO-8A@mail.gmail.com>

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 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
> > <pkg-name>" to
> > > > build it.
> > > >
> > >
> > > But then when I do ptxdist targetinstall <pkg-name>, 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 <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:
> 
> When I do ptxdist targetinstall <pkg-name>, 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.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-11-02 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 17:28 Guillermo Rodriguez Garcia
2017-11-01 11:01 ` Michael Olbrich
2017-11-02 12:20   ` Guillermo Rodriguez Garcia
2017-11-02 12:38     ` Michael Olbrich
2017-11-02 14:09       ` Andreas Glatz
2017-11-02 15:19       ` Guillermo Rodriguez Garcia
2017-11-02 15:33         ` Michael Olbrich [this message]
2017-11-02 15:50           ` Guillermo Rodriguez Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171102153335.23xsmv63pqlytedw@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox