mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] Building packages but not including them in the the resulting firmware image
@ 2020-02-14 17:33 Mircea Ciocan
  2020-02-14 17:58 ` Mircea Ciocan
  2020-02-15  9:20 ` Michael Olbrich
  0 siblings, 2 replies; 3+ messages in thread
From: Mircea Ciocan @ 2020-02-14 17:33 UTC (permalink / raw)
  To: ptxdist

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-02-15  9:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-14 17:33 [ptxdist] Building packages but not including them in the the resulting firmware image Mircea Ciocan
2020-02-14 17:58 ` Mircea Ciocan
2020-02-15  9:20 ` Michael Olbrich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox