From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org, openembedded-devel@lists.openembedded.org
Subject: Re: [yocto] LAMP layer
Date: Wed, 27 Jun 2012 16:58:39 +0100 [thread overview]
Message-ID: <1653998.N39MDkghNa@helios> (raw)
In-Reply-To: <CAMKF1spB5Q3BHhbbnf6ARfJBZ=si-LE-7wYw07w=_ODSG4dPOA@mail.gmail.com>
On Wednesday 27 June 2012 08:49:22 Khem Raj wrote:
> I think PHP probably is common enough to be part
> of meta-oe or core. instead of lamp call it something else may be
> meta-webservers or something
> and more alternatives can also be put in there
I don't know a huge amount about PHP but it appears to me that it can be built
either standalone or as an Apache module - we had two separate recipes to
build each alternative in OE-classic, and that split persists today - the
standalone version is in meta-oe and I'm resurrecting the apache module
version (modphp).
I don't think PHP belongs in OE-core - it's not something everyone needs. I'm
willing to accept the standalone version might also belong in this layer
though particularly if it turns into a more generic web server layer as you're
suggesting. I'm not sure I can commit to cleaning up the standalone version
though.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org, openembedded-devel@lists.openembedded.org
Subject: Re: LAMP layer
Date: Wed, 27 Jun 2012 16:58:39 +0100 [thread overview]
Message-ID: <1653998.N39MDkghNa@helios> (raw)
In-Reply-To: <CAMKF1spB5Q3BHhbbnf6ARfJBZ=si-LE-7wYw07w=_ODSG4dPOA@mail.gmail.com>
On Wednesday 27 June 2012 08:49:22 Khem Raj wrote:
> I think PHP probably is common enough to be part
> of meta-oe or core. instead of lamp call it something else may be
> meta-webservers or something
> and more alternatives can also be put in there
I don't know a huge amount about PHP but it appears to me that it can be built
either standalone or as an Apache module - we had two separate recipes to
build each alternative in OE-classic, and that split persists today - the
standalone version is in meta-oe and I'm resurrecting the apache module
version (modphp).
I don't think PHP belongs in OE-core - it's not something everyone needs. I'm
willing to accept the standalone version might also belong in this layer
though particularly if it turns into a more generic web server layer as you're
suggesting. I'm not sure I can commit to cleaning up the standalone version
though.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-27 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 14:05 LAMP layer Paul Eggleton
2012-06-27 14:26 ` Marcin Juszkiewicz
2012-06-27 15:22 ` Jack Mitchell
2012-06-27 15:57 ` Tomas Frydrych
2012-06-27 16:27 ` Paul Eggleton
2012-06-27 16:40 ` Jack Mitchell
2012-06-27 16:49 ` Paul Eggleton
2012-06-27 18:01 ` Khem Raj
2012-06-28 9:12 ` Paul Eggleton
2012-06-27 15:49 ` [yocto] " Khem Raj
2012-06-27 15:49 ` Khem Raj
2012-06-27 15:58 ` Paul Eggleton [this message]
2012-06-27 15:58 ` 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=1653998.N39MDkghNa@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.