From: Vlastimil Setka <setka@rexcontrols.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Ptxdist / DistroKit Questions
Date: Sun, 9 Jul 2017 15:09:21 +0200 [thread overview]
Message-ID: <cbd9ba3a-62d7-0611-a67e-1414b842ca38@rexcontrols.com> (raw)
Hello,
after using ptxdist with DistroKit as a reference BSP for a while, I
have several questions and ambiguities about some dark corners:
# Is it possible to built some packages into .ipk files, but do not
include them by default in the image? I thought that the [M] option
available in menuconfig could be intended for this, but seems it does
not work this way. Btw, what the [M] option really do differently from [*]?
# (maybe extension of previous question) How to manage ptxdist
configuration for multiple boards sharing the same CPU architecture and
all base packages? Some boards needs some additional packages for
specific HW, or specific application cases. Or the requirement could be
to have minimal image and full-featured image for the same board. It
would be nice to have some way how to build multiple images -- with
multiple different _rootfs_ images -- with different package (and maybe
additional files) sets.
# How the ${PTXDIST_BSP_AUTOVERSION} works? With current DistroKit from
git, I'm allways getting
"OSELAS(R)-DistroKit-????.??.?-?-g76e1280aca97-dirty-1 /
v7a-????.??.?-?-g76e1280aca97-dirty". Similar problem with ???? version
is in the doc files built from current git. Maybe some tag is missing in
the git?
Regards, Vlastimil
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2017-07-09 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 13:09 Vlastimil Setka [this message]
2017-07-09 19:42 ` Alexander Dahl
2017-07-17 8:01 ` 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=cbd9ba3a-62d7-0611-a67e-1414b842ca38@rexcontrols.com \
--to=setka@rexcontrols.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