It is in a git repo. The same git repo as my other tool. It's just entangled in a number of other things right now that I need to disentangle. There is 5 years of history in building this in that repo. Also 5 years of seeing what works in precisely the use case this solves: checking the requirements of a developer's computer and making sure the right packages are installed so they can proceed.
The reason it is written in bash, and not python, is because python is not universally available on all distros out of the box. This is why python is listed in the package list for every distro in the setup documentation. Remember this isn't about choose your favourite language, it's about using bootstrapping a build environment. There is literally nothing you need to do other than download it and run it on the distros most people use. I wrote it in bash (and related utilities) because bash is always there. And considering ready-for.sh (what check-requirements.sh is based on) has successfully been run (minimally) thousands of times successfully (probably a lot higher since it is also used for the LF MOOC) I stand by this decision. And again this is not intended to be an OE or YP only thing. Again this is being maintained alongside an existing tool and shares more than 90% of the code with ready-for.sh. Moving or rewriting it in $LANGUAGE means essentially forking it. Behan Sent from my Mobile Computer which is also a phone > On 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 >> Openembeddedfirstname.lastname@example.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- _______________________________________________ Openembedded-devel mailing list Openembeddedemail@example.com http://lists.openembedded.org/mailman/listinfo/openembedded-devel