All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: Martin Dietze <di@fh-wedel.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] PCRE breakage [libpcre: added new port]
Date: Mon, 11 Sep 2006 09:03:26 +1000	[thread overview]
Message-ID: <20060910230325.GA9890@twibble.org> (raw)
In-Reply-To: <20060910085502.GH17558@fh-wedel.de>

On Sun, Sep 10, 2006 at 10:55:02AM +0200, Martin Dietze wrote:
> On Sat, September 09, 2006, Michael 'Mickey' Lauer wrote:
> 
> > > You added libpcre and removed pcre and in the process you've also:
> > > 
> > >  - Broken 20+ recipes which DEPEND on pcre. These would all need to
> > >    be modified to depend on libpcre now instead.
> 
> Something made me think there was no such package (pcre). Seems 

Ah, that make sense. I could have fixed this all up when you
submitted it, but I could not decide on exactly what you were doing,
so wanted some confirmation on that first.

> like I need to reduce my number of working hours :/ 

I think we all need that ;)

> Will fix this as first thing on Monday.

Others have fixed most of it by now (the missing LICENSE is about all
that needs to be added now). It's probably a good idea to just
compare the old (now deleted) pcre/pcre_4.4.bb with your new
libpcre/libpcre_4.4.bb and make sure everything from the old one is
in there.

Thanks.

-- 
 Jamie Lenehan <lenehan@twibble.org>



      reply	other threads:[~2006-09-10 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GLfnq-00056C-UM@linuxtogo.org>
2006-09-09  4:43 ` PCRE breakage [libpcre: added new port] Jamie Lenehan
2006-09-09  4:45   ` Jamie Lenehan
2006-09-09 12:40     ` pHilipp Zabel
2006-09-09 13:30   ` [oe-commits] " Michael 'Mickey' Lauer
2006-09-10  8:55     ` Martin Dietze
2006-09-10 23:03       ` Jamie Lenehan [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=20060910230325.GA9890@twibble.org \
    --to=lenehan@twibble.org \
    --cc=di@fh-wedel.de \
    --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.