From: Denys Dmytriyenko <denys@ti.com>
To: <meta-ti@yoctoproject.org>
Subject: RFC: 2 possible workarounds for recipes-misc dependency on Angstrom
Date: Fri, 14 Sep 2012 02:43:07 -0400 [thread overview]
Message-ID: <20120914064306.GC26968@edge> (raw)
Koen et al,
There will be 2 patches sent under this thread that try to resolve the
dependency of recipes-misc/images on meta-angstrom layer w/o (re)moving those
recipes. Those are just 2 possible alternatives of fixing it up for now. The
third option would be to move the recipes-misc/images to another layer, once
we agree on its name/location and other details. Nobody wants to just remove
those recipes w/o giving them a proper home. Which also means, that one of the
proposed 2 workarounds can still be used temporarily until such home is found.
[Or, one of the two can be the final solution, if we decide not to move...]
Please at least consider these patches and don't blindly dismiss them, as this
matter is quite a hot button.
--
Denys
next reply other threads:[~2012-09-14 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 6:43 Denys Dmytriyenko [this message]
2012-09-14 6:46 ` [RFC: PATCH 1] ti-hw-bringup-image: fix 'no LICENSE' parsing error when meta-angstrom is not used Denys Dmytriyenko
2012-09-14 6:47 ` [RFC: PATCH 2] systemd-image: overlay local copy to enable building ti-hw-bringup-image Denys Dmytriyenko
2012-09-14 20:06 ` RFC: 2 possible workarounds for recipes-misc dependency on Angstrom Maupin, Chase
2012-09-17 20:36 ` Enrico
2012-09-17 20:42 ` Koen Kooi
2012-09-17 21:50 ` Denys Dmytriyenko
2012-09-17 23:27 ` Enrico
2012-09-17 20:54 ` Philip Balister
2012-09-17 21:47 ` Denys Dmytriyenko
2012-09-17 21:55 ` Denys Dmytriyenko
2012-09-18 0:16 ` Enrico
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=20120914064306.GC26968@edge \
--to=denys@ti.com \
--cc=meta-ti@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.