All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: [PATCH 0/5] *.bbclass: search configs in D instead of S
Date: Sun, 17 Apr 2011 01:23:04 +0200	[thread overview]
Message-ID: <1302996184.3122.30.camel@utx.lan> (raw)

Following series of patches changes way how config files are populated.
Searching for *-config and .pc config files in S makes more problems
than it brings benefits. Searching in the installed root seems to be
more logical.

Fixes following subtle breakages:
- files are populated with a different name that upstream intended
- populated files that were not intended to be populated

It was discussed previously here:
http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-January/029261.html

Now I was able to make a complete system build with these patches, so I
guess that they are ready to be pushed. I am sending class changes for
review and waiting for ACK of class changes.

Packages that are known to be fixed by this change:
ncurses
PR update will be needed here. (Not sending this patch to the list.)

Packages that need to be modified after this change:
tcl
tk
I already have these patches ready - just remove custom staging and use
standard staging way plus simple trick. (Not sending this patch to the
list.)

Packages with secondary breakage fixed by this patch set:
alsa-utils (breakage triggered by ncurses)

New packages that may be build with this patch set:
lynx

-- 

________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




             reply	other threads:[~2011-04-16 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 23:23 Stanislav Brabec [this message]
2011-04-19 11:22 ` [PATCH 0/5] *.bbclass: search configs in D instead of S Andreas Oberritter
2011-04-20 15:40   ` Stanislav Brabec

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=1302996184.3122.30.camel@utx.lan \
    --to=utx@penguin.cz \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paulepanter@users.sourceforge.net \
    /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.