mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] How to create multiple packages, which contain same filename ?
Date: Tue, 11 Dec 2018 08:58:02 +0000	[thread overview]
Message-ID: <8511997be26a8a2cfc65ed9474a88c67ec60c5d8.camel@allegion.com> (raw)
In-Reply-To: <CAA0ZWqbCwRjx3kHuDKo06DVzrLrU0Y7+zs-CWcuZATr-q1RsnA@mail.gmail.com>

Hi Andreas,

this use case is supported by ptxdist, actually quite exactly as you planned it.

You will eventually run into this issue:

https://www.mail-archive.com/ptxdist@pengutronix.de/msg13611.html

But probably only if you use image packages for creating your three rootfses at
the same time (saves a lot of build time btw).


Best Regards
Florian

Am Donnerstag, den 06.12.2018, 12:49 +0100 schrieb Andreas Friesen:
> Hello everyone,
> 
> we've got many module types, each module type  builds on same platform. I
> would like create a generic barebox environment for all module types.
> 
> My problem is, that ptxdist  don't like packages, which contain same filename.
> My plan was to create several packages : 
> 
> - firmware-Type-A.ipkg (contains /boot/{fpga.bin,platform.dtb)
> - firmware-Type-B.ipkg (contains  /boot/{fpga.bin,platform.dtb)
> - firmware-Type-C.ipkg (contains  /boot/{fpga.bin,platform.dtb)
> 
> And each module install via" collection" the respective package.
> 
> What can I do ? I would like to avoid having foreign components in the
> firmware package.
> 
> Regards,
> Andreas Friesen
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2018-12-11  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 11:49 Andreas Friesen
2018-12-11  7:29 ` Michael Olbrich
2018-12-11  8:58 ` Baeuerle, Florian [this message]
2018-12-11 10:59   ` Andreas Friesen
2018-12-11 11:13     ` Baeuerle, Florian
2018-12-14 10:57       ` Andreas Friesen
2018-12-14 11:51         ` Baeuerle, Florian

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=8511997be26a8a2cfc65ed9474a88c67ec60c5d8.camel@allegion.com \
    --to=florian.baeuerle@allegion.com \
    --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