From: Alexander Dahl <post@lespocky.de>
To: PTXdist Developer Mailinglist <ptxdist@pengutronix.de>
Subject: [ptxdist] installing different config files for lighttpd depending on some config variable
Date: Wed, 09 Nov 2011 13:26:48 +0100 [thread overview]
Message-ID: <ed6a071e10906b08e187c3b5e29a3961@idefix.lespocky.dyndns.org> (raw)
Hei hei,
we build or BSP in different configurations depending on some options
in the menuconfig, see:
choice
prompt "Vendor name "
config VENDOR_FOO
bool
prompt "foo"
config VENDOR_BAR
bool
prompt "bar"
config VENDOR_BAZ
bool
prompt "baz"
endchoice
This is evaluated in several rules and in combination with collections
works quite well. In all configurations we use lighttpd as webserver,
previously with equal lighttpd.conf, but now we need different webserver
configs for each vendor/collection.
I could copy the rules/lighttpd.make from ptxdist distribution to our
BSP now and adapt it, but this would require manual attention on merging
both with each migration to a new ptxdist release and I'd like to avoid
that.
I came across the possibility of postinst/preinst scripts in
targetinstall stage and assume I could use this. A preinst script would
populate projectroot/etc/lighttpd/lighttpd.conf with the right config
just before install_alternative() is called inside the distributed rule.
If this is a reasonable idea, where do I find documentation to these
preinst/postinst stuff? The »Don't Panic« guide doesn't cover this
topic. :-/
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2011-11-09 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 12:26 Alexander Dahl [this message]
2011-11-09 17:09 ` 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=ed6a071e10906b08e187c3b5e29a3961@idefix.lespocky.dyndns.org \
--to=post@lespocky.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