[ptxdist] Building packages but not including them in the the resulting firmware image

[ptxdist] Building packages but not including them in the the resulting firmware image

[Mircea Ciocan]

Hello everybody, I'm trying to implement the following solution:

I have a base firmware image configuration and a number of optional 
packages, for some later choices of the customers.

I don't want to have the optional packages installed in the base 
firmware image at all, no matter the choices, but have them as 
installable packages in separate IPKs for later use.

So far, playing with the, rather sparse documented, feature of 
_collections_, I was only able to build different monolithic firmware 
versions, when I was marking the optional packages with "m" and with "y" 
in the collection file.

The separate IPKs are build, but they're also installed in the fw image, 
I didn't find a way to build them as packages and exclude form 
installing in the firmware image.

Is there currently a way to that during a single run, to build the base 
firmware and alongside of it, separate IPKs to be installed later with 
OPKG ?

So far right, now I have to do two runs, one with collections and one 
without and discard the "fat" resulting image, which is rather cumbersome.


  Best regards,

  Mircea C.





_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Building packages but not including them in the the resulting firmware image

[Mircea Ciocan]

It's lame to reply to your messages, but as always, right after posting 
a question, the answer pops up and it's embarrassingly obvious.

Kindly please disregard and sorry for the noise.


Best regards,

Mircea C.


On 14.02.20 18:33, Mircea Ciocan wrote:
> Hello everybody, I'm trying to implement the following solution:
>
> I have a base firmware image configuration and a number of optional 
> packages, for some later choices of the customers.
>
> I don't want to have the optional packages installed in the base 
> firmware image at all, no matter the choices, but have them as 
> installable packages in separate IPKs for later use.
>
> So far, playing with the, rather sparse documented, feature of 
> _collections_, I was only able to build different monolithic firmware 
> versions, when I was marking the optional packages with "m" and with 
> "y" in the collection file.
>
> The separate IPKs are build, but they're also installed in the fw 
> image, I didn't find a way to build them as packages and exclude form 
> installing in the firmware image.
>
> Is there currently a way to that during a single run, to build the 
> base firmware and alongside of it, separate IPKs to be installed later 
> with OPKG ?
>
> So far right, now I have to do two runs, one with collections and one 
> without and discard the "fat" resulting image, which is rather 
> cumbersome.
>
>
>  Best regards,
>
>  Mircea C.
>
>
>
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de



_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Building packages but not including them in the the resulting firmware image

[Michael Olbrich]

On Fri, Feb 14, 2020 at 06:33:51PM +0100, Mircea Ciocan wrote:
> Hello everybody, I'm trying to implement the following solution:
> 
> I have a base firmware image configuration and a number of optional
> packages, for some later choices of the customers.
> 
> I don't want to have the optional packages installed in the base firmware
> image at all, no matter the choices, but have them as installable packages
> in separate IPKs for later use.
> 
> So far, playing with the, rather sparse documented, feature of
> _collections_, I was only able to build different monolithic firmware
> versions, when I was marking the optional packages with "m" and with "y" in
> the collection file.
> 
> The separate IPKs are build, but they're also installed in the fw image, I
> didn't find a way to build them as packages and exclude form installing in
> the firmware image.
> 
> Is there currently a way to that during a single run, to build the base
> firmware and alongside of it, separate IPKs to be installed later with OPKG
> ?
> 
> So far right, now I have to do two runs, one with collections and one
> without and discard the "fat" resulting image, which is rather cumbersome.

There are multiple ways to do this. If the packages that are left out are
all defined in your BSP then you can modify the rule:

EXTRA_PACKAGES-$(PTXCONF_FOO) += foo

All extra packages are built but not added to the roofs by default.

Or you can modify the list of packages that are built into to rootfs. If
you use the regular images that means overwriting image-root-tgz.make and
setting:

IMAGE_ROOT_TGZ_PKGS	= $(call ptx/collection, $(call ptx/in-path,PTXDIST_PATH_LAYERS,configs/collectionconfig))

With something like this you could also create multiple images, with and
without the extra packages in one build. These features are documented[1]
but with a different use-case in mind.

Michael

[1] https://www.ptxdist.org/doc/daily_work_section.html#creating-individual-root-filesystems-for-each-variant

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de