From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: Mircea Ciocan <m.ciocan@ppc-ag.de>
Subject: Re: [ptxdist] Adding package independent files in the root filesystem
Date: Fri, 19 Jun 2020 13:31:07 +0200 [thread overview]
Message-ID: <20200619113105.7tq3ojypjqkhxey7@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <d0b29c54-0afd-5cb6-9932-8e1b51b27d9e@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1900 bytes --]
Hei hei,
On Fri, Jun 19, 2020 at 10:08:14AM +0200, Bastian Krause wrote:
> On 6/19/20 9:51 AM, Mircea Ciocan wrote:
> > I have some configuration files that are package independent, but board
> > depended, is there a solution to add them in bulk to the root filesystem.
> >
> > It seem that configs/platform-XXX/projectroot only holds configuration
> > files that overrides the default ALREADY EXISTING files in the root file
> > system, all other files seem to be ignored.
> >
> > Is there some "magic" setting that allows a full projectroot copy and
> > overwrite/add the content to the rootfs or is there another way to get a
> > similar effect ?
Create another package for those files. That's what we did at work in
our BSPs.
> Only files that are installed by an enabled package using
> install_alternative(_tree) [1][2] are taken from projectroot.
>
> Create a new target package with "ptxdist newpackage target", remove
> everything but PACKAGES-$(PTXCONF_YOURPACKAGE), YOURPACKAGE_VERSION,
> YOURPACKAGE_LICENSE and the targetinstall stage. In the targetinstall
> stage you can use install_alternative_tree [2] to install "the whole
> source directory tree with all files" [2].
I would suggest `ptxdist newpackage file` which seems to be the
template for exactly that usecase. Of course you could go with every
other template and adapt it or create a package from scratch, but the
'file' template gives you a very simple .in rule and a .make rule with
just the targetinstall stage active, you don't need more to just
install some files to the target.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2020-06-19 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 7:51 Mircea Ciocan
2020-06-19 8:08 ` Bastian Krause
2020-06-19 11:31 ` Alexander Dahl [this message]
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=20200619113105.7tq3ojypjqkhxey7@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=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