From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org, yocto@yoctoproject.org
Cc: joe.macdonald@windriver.com
Subject: LAMP layer
Date: Wed, 27 Jun 2012 15:05:08 +0100 [thread overview]
Message-ID: <20317992.tBZ1YY1I5v@helios> (raw)
Hi all,
In conjunction with the folks at Wind River I'm currently in the process of
putting together a layer to support the traditional LAMP stack, and wanted to
solicit some opinions on how this might be structured/named/etc.
I think we have the "L" pretty much covered ;) and we have MySQL in meta-oe
(I'm not convinced that's where it should stay, although perhaps it need not
be tied to this layer either). So the layer would at the very least be adding
Apache and PHP, with the possibility of web-related python and perl recipes
being added at a later date.
Some of the other things I'm looking at adding more immediately:
* collectd
* mysql-connector-odbc
* phpMyAdmin
* unixODBC
* xdebug
The question of how this should all be structured is still not fully
determined. I'm thinking this ought to be at least one additional layer (i.e.
meta-lamp, or some other name), even in the face of the proposed meta-
networking, since the number of recipes in the LAMP layer is likely to grow
over time and it's a specific set of functionality that people would explicitly
select.
I now have updated apache and modphp recipes building and working reasonably
well, although further testing will be needed. Initially I'm prepared to
maintain these recipes, however if not immediately at some point in the near
future it would be good to see a maintainer step forward with more specific
knowledge of these particular pieces of software.
Thoughts?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2012-06-27 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 14:05 Paul Eggleton [this message]
2012-06-27 14:26 ` LAMP layer 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 ` [yocto] " Paul Eggleton
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=20317992.tBZ1YY1I5v@helios \
--to=paul.eggleton@linux.intel.com \
--cc=joe.macdonald@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--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.