Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver] modphp
Date: Thu, 10 Mar 2016 14:36:51 +0100	[thread overview]
Message-ID: <20160310133651.GG2573@jama> (raw)
In-Reply-To: <56E1712A.9070102@mlbassoc.com>

[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]

On Thu, Mar 10, 2016 at 02:05:46PM +0100, Gary Thomas wrote:
> On 2016-03-10 14:02, Martin Jansa wrote:
> > On Thu, Mar 10, 2016 at 01:18:59PM +0100, Gary Thomas wrote:
> >> On 2016-03-10 11:55, Martin Jansa wrote:
> >>> On Thu, Mar 10, 2016 at 10:41:25AM +0100, Gary Thomas wrote:
> >>>> Anyone know what happened to the recipe for modphp which was
> >>>> in meta-oe (maybe before meta-webserver) circa 2013?  I can't
> >>>> find a recipe for this anywhere.
> >>>
> >>> Why not try git log?
> >>
> >> Of course!  I don't often search logs for things I don't know where
> >> to find though.
> >>
> >> An aside - doesn't this change make meta-oe depend on meta-webserver
> >> (which doesn't seem like a positive relationship)?
> >
> > What in meta-oe depends on meta-webserver? I don't see anything.
> 
> Select 'apache2' in the package config for php - that would then require
> recipe(s) from meta-webserver

That's OK as long as apache2 isn't in default PACKAGECONFIG.

There are couple optional dependencies even in oe-core's PACKAGECONFIGs
which require other layers.

> >>> commit f81961ff20d669e0f472f45b9922d6f62ee0d330
> >>> Author: Paul Eggleton <paul.eggleton@linux.intel.com>
> >>> Date:   Mon Jan 5 10:24:53 2015 +0000
> >>>
> >>>       README: update for modphp merging into php
> >>>
> >>>       Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> >>>
> >>> commit 06af52095b5be1cb21a7dc9a6a6e05d01f6e7a00
> >>> Author: Paul Eggleton <paul.eggleton@linux.intel.com>
> >>> Date:   Thu Jan 1 23:34:29 2015 +0000
> >>>
> >>>       modphp: remove
> >>>
> >>>       This is now built out of the standard php recipe.
> >>>
> >>>       Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-03-10 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  9:41 [meta-webserver] modphp Gary Thomas
2016-03-10 10:55 ` Martin Jansa
2016-03-10 12:18   ` Gary Thomas
2016-03-10 13:02     ` Martin Jansa
2016-03-10 13:05       ` Gary Thomas
2016-03-10 13:36         ` Martin Jansa [this message]
2016-03-10 13:36           ` Gary Thomas

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=20160310133651.GG2573@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox