From: Juergen Hoetzel <gentoo@hoetzel.info>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proposal: config files for php extensions
Date: Mon, 14 Mar 2005 13:39:07 +0100 [thread overview]
Message-ID: <20050314123907.GA713@h5331.serverkompetenz.net> (raw)
Hi,
http://bugs.gentoo.org/show_bug.cgi?id=85082 made me consider about
third-party php-extensions modifying php.ini. Why doesn't php ebuilds
use the scan-dir feature ('--with-config-file-scan-dir=/etc/php.d') like
RedHats do?
Every third-party extension gets its own config file
(/etc/php.d/extension.ini) and unmerging will be no pain anymore.
The following php extensions modify the global php.ini, by using
php-ext-base_addtoinifiles (module specific entries entry)
and php-ext-source_src_install (extension=extension.so entry):
dev-php/PECL-apc
dev-php/php-accelerator
dev-php/phpdbg
dev-php/turck-mmcache
dev-php/accelerator
But with more extensions to appear, php.ini will get more
complex.
Jürgen
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-03-14 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 12:39 Juergen Hoetzel [this message]
2005-03-14 14:46 ` [gentoo-dev] Proposal: config files for php extensions Mike Frysinger
2005-03-14 16:29 ` Juergen Hoetzel
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=20050314123907.GA713@h5331.serverkompetenz.net \
--to=gentoo@hoetzel.info \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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