mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Mircea Ciocan <m.ciocan@ppc-ag.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building packages but not including them in the the resulting firmware image
Date: Fri, 14 Feb 2020 18:58:06 +0100	[thread overview]
Message-ID: <0b560ec0-d286-5a16-ab4d-efed6e661596@ppc-ag.de> (raw)
In-Reply-To: <05f02949-036c-15b9-41ad-fce25b8638cf@ppc-ag.de>

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

  reply	other threads:[~2020-02-14 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 17:33 Mircea Ciocan
2020-02-14 17:58 ` Mircea Ciocan [this message]
2020-02-15  9:20 ` Michael Olbrich

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=0b560ec0-d286-5a16-ab4d-efed6e661596@ppc-ag.de \
    --to=m.ciocan@ppc-ag.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