Also, I recommend a method of linking the checker script with the documentation. And run unit tests to prove nothing has changed on distro X, Y or Z. And I want a pony, with wings and a single horn.
On Thu, Aug 10, 2017 at 1:38 AM Tim Orling <ticot...@gmail.com> wrote: > So where does it live? It ends up being: run shell script from > "somewhere". I know what you mean about git and other requirements, but > still it must be sourced from "somewhere". If you add a desire to be > version controlled, it then logically lands in a git repo. Or subversion, > bazaar or mercurial. > > Thinking outside the box, we could make it a python (humor me) module > installed from pypi and document how to run it... > > I tend to use shell scripts as my first draft and then translate to > python. This usually means a lot of "subprocess" calls and is by no means a > silver bullet. > > Alternatively, it becomes a clickable link on a website. That means > nodejs. Or perl. Or... > On Wed, Aug 9, 2017 at 9:40 PM Behan Webster <beh...@converseincode.com> > wrote: > >> > On Aug 9, 2017, at 7:22 AM, Leonardo Sandoval < >> leonardo.sandoval.gonza...@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. >> >> Behan >> -- >> _______________________________________________ >> Openembedded-devel mailing list >> Openembedded-devel@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> > -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel