mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Andreas Helmcke <ahelmcke@ela-soft.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/2] php: reanimate PHP as PHP8
Date: Fri, 10 Jun 2022 11:42:31 +0200	[thread overview]
Message-ID: <97c41aaf-ea0e-c0e7-5e34-88e18a9c4329@ela-soft.com> (raw)
In-Reply-To: <YqLidp9ScWCqTEBf@pengutronix.de>


Hello,

Am 10.06.22 um 08:19 schrieb Michael Olbrich:
> On Fri, Jun 03, 2022 at 05:12:08PM +0200, Andreas Helmcke wrote:
>> +
>> +ifdef PTXCONF_PHP8_SAPI_CGI
>> +    @$(call install_copy, php8, 0, 0, 0755, -, /usr/bin/php-cgi)
>> +endif
>> +
>> +ifdef PTXCONF_PHP8_INI
>> +    @$(call install_alternative, php8, 0, 0, 0644, /etc/php8/php.ini)
>
> php8 does not install this, so you need to add on to ptxdist in
> projectroot/.
>

php8 does provide templates for php.ini. I would like to use this file:
.../build-target/php-8.1.6/php.ini-production

I'd like to have ptxdist to install php.ini from the users project root, if provided (just like install_alternative does) but copy php-ini-production as php.ini, if install_alternative does not find a source.

I think I can achieve this just with copying php.ini-production to ptxdist projectroot/ but then with each version bump this has to be done manually again.

Is there a better solution?

Andreas 



  reply	other threads:[~2022-06-10  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 16:55 [ptxdist] [PATCH " Andreas Helmcke
2022-06-03  7:07 ` Michael Olbrich
2022-06-03 15:12   ` [ptxdist] [PATCH v2 " Andreas Helmcke
2022-06-09 18:00     ` Michael Olbrich
2022-06-10  6:19     ` Michael Olbrich
2022-06-10  9:42       ` Andreas Helmcke [this message]
2022-06-13 19:25       ` [ptxdist] [PATCH v3 " Andreas Helmcke
2022-06-20  6:19         ` [ptxdist] [APPLIED] " 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=97c41aaf-ea0e-c0e7-5e34-88e18a9c4329@ela-soft.com \
    --to=ahelmcke@ela-soft.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