From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Behan Webster <behanw@converseincode.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Alpha release of check-requirement.sh
Date: Thu, 10 Aug 2017 09:26:52 -0500 [thread overview]
Message-ID: <1502375212.29285.17.camel@linux.intel.com> (raw)
In-Reply-To: <879E7479-CCE4-47D5-BB40-E789BA93185C@converseincode.com>
On Wed, 2017-08-09 at 21:40 -0700, Behan Webster wrote:
> > On Aug 9, 2017, at 7:22 AM, Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
> >
> > in my opinion, this fits nicely into the oe-core, into the
> > scripts/contrib folder.
>
> Keeping it in script/contrib seems odd to me (horse before the cart). One of the requirements for OE is git (or tar) to actually get OE in the first place.
>
> I see this as more something some one would run before cloning OE or Poky. It’s a replacement for needing to read a long HOWTO on a webpage to get started with OE or YP.
this installation way can help
$ curl <path to the script inside git repo> | sh
>
> Behan
next prev parent reply other threads:[~2017-08-10 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 0:24 Alpha release of check-requirement.sh Behan Webster
2017-08-09 14:22 ` Leonardo Sandoval
2017-08-09 18:32 ` Randy MacLeod
2017-08-10 4:37 ` Behan Webster
2017-08-10 4:40 ` Behan Webster
2017-08-10 8:38 ` Tim Orling
2017-08-10 8:42 ` Tim Orling
2017-08-10 16:49 ` Behan Webster
2017-08-10 16:54 ` Behan Webster
2017-08-10 15:16 ` Behan Webster
2017-08-10 14:26 ` Leonardo Sandoval [this message]
2017-08-10 18:11 ` Behan Webster
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=1502375212.29285.17.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=behanw@converseincode.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 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.