Re: [ptxdist] How to create "hotfix" packages

[Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2654 bytes --]

2017-11-02 13:38 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.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 "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
> <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.

Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 3969 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de