From: Jack Mitchell <ml@communistcode.co.uk>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 0/3] php: further clean-ups
Date: Mon, 29 Apr 2013 14:44:24 +0100 [thread overview]
Message-ID: <517E7938.1000200@communistcode.co.uk> (raw)
In-Reply-To: <20130429134047.GI3199@jama>
On 29/04/13 14:40, Martin Jansa wrote:
> On Mon, Apr 29, 2013 at 02:23:39PM +0100, Jack Mitchell wrote:
>> From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
>>
>> Few more PHP clean-up patches, some testing on more esoteric hardware would
>> be nice, but I don't forsee any problems (famous last words...).
> Thanks for cleanup patches, are you also using modphp? In last jenkins
> builds I've noticed that php and modphp recipes are trying to install
> conflicting files in sysroot (and only first one successfully) can you
> check if they can be altered to install them correctly or even better,
> there was some thread about building cgi and fpm together, what about
> building all 4 +cli +modphp in one recipe with few PACKAGECONFIGs?
>
> Cheers,
>
>
I think that would be a fantastic idea, I don't really understand why
modphp and php are different recipes really.
However, I don't use modphp and I'm not sure I have the skills to merge
them properly. I will have a look and see if I can do anything.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2013-04-29 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 13:23 [meta-oe][PATCH 0/3] php: further clean-ups Jack Mitchell
2013-04-29 13:23 ` [meta-oe][PATCH 1/3] php: remove obsolete CFLAGS Jack Mitchell
2013-04-29 13:23 ` [meta-oe][PATCH 2/3] php: remove unnecessary LIBS export Jack Mitchell
2013-04-29 13:23 ` [meta-oe][PATCH 3/3] php: remove unneeded THREADS export Jack Mitchell
2013-04-29 13:40 ` [meta-oe][PATCH 0/3] php: further clean-ups Martin Jansa
2013-04-29 13:44 ` Jack Mitchell [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=517E7938.1000200@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=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.