From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 03/11] php: integrate modphp
Date: Fri, 2 Jan 2015 18:41:08 +0100 [thread overview]
Message-ID: <20150102174108.GI2469@jama> (raw)
In-Reply-To: <loom.20150102T180131-945@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
On Fri, Jan 02, 2015 at 05:10:34PM +0000, Paul Eggleton wrote:
> Martin Jansa <martin.jansa <at> gmail.com> writes:
> > On Fri, Jan 02, 2015 at 09:31:58AM +0000, Paul Eggleton wrote:
> > > Build the mod-php Apache module within the main php recipe; this avoids
> > > files in the sysroot from stepping on eachother and therefore avoids the
> > > resulting build failure.
> > >
> > > Changes made:
> > > * Add an "apache2" PACKAGECONFIG, default enabled. This does mean that
> > > apache2 is a build dependency by default; if you don't want this,
> > > set your own PACKAGECONFIG value for the php recipe.
> >
> > I think it should be disabled by default, because meta-oe layer doesn't
> > depend on meta-webserver layer where apache2 lives.
>
> You're right, somehow I completely missed that - sorry. I'll fix in v2 on
> Monday.
>
> > meta-webserver can have .bbappend which will add it to PACKAGECONFIG for
> > xdebug to work with default php recipe.
>
> As you may recall I'm of the opinion that software layers should not be
> setting the policy of other layers, so I don't think this is really
> appropriate; I'll just have to live with the fact that users who want it
> will need to enable it themselves. In any case by the end of the patchset,
> xdebug depends on php rather than modphp so it should still build fine
> without apache2 in PACKAGECONFIG.
Ah, ok, I was assuming that xdebug depends on php with apache2
PACKAGECONFIG enabled.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-01-02 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 9:31 [meta-oe/meta-webserver][PATCH 00/11] Merge modphp into php and upgrade Paul Eggleton
2015-01-02 9:31 ` [meta-oe][PATCH 01/11] php: upgrade to 5.5.15 Paul Eggleton
2015-01-02 9:31 ` [meta-oe][PATCH 02/11] libc-client: rename to uw-imap, upgrade to 2007f Paul Eggleton
2015-01-02 9:31 ` [meta-oe][PATCH 03/11] php: integrate modphp Paul Eggleton
2015-01-02 12:49 ` Martin Jansa
2015-01-02 17:10 ` Paul Eggleton
2015-01-02 17:41 ` Martin Jansa [this message]
2015-01-02 9:31 ` [meta-oe][PATCH 04/11] php: upgrade to 5.5.20 Paul Eggleton
2015-01-02 9:32 ` [meta-webserver][PATCH 05/11] modphp: remove Paul Eggleton
2015-01-02 9:32 ` [meta-oe][PATCH 06/11] uw-imap: make libpam dependency dependent on DISTRO_FEATURES Paul Eggleton
2015-01-02 12:47 ` Martin Jansa
2015-01-02 16:39 ` Paul Eggleton
2015-01-02 9:32 ` [meta-oe][PATCH 07/11] php: add PACKAGECONFIG to fix implicit dependency on libpam Paul Eggleton
2015-01-02 9:32 ` [meta-oe][PATCH 08/11] php: add PACKAGECONFIG for imap Paul Eggleton
2015-01-02 9:32 ` [meta-webserver][PATCH 09/11] xdebug: fix DEPENDS and un-blacklist Paul Eggleton
2015-01-02 9:32 ` [meta-webserver][PATCH 10/11] xdebug: update to 2.2.6 Paul Eggleton
2015-01-02 9:32 ` [meta-webserver][PATCH 11/11] phpmyadmin: update to 4.3.4 Paul Eggleton
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=20150102174108.GI2469@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.