On 9/6/2010 3:03 AM, Dave Neary wrote:
Hi,

Marius Vollmer wrote:
In general, I think we don't need to treat the shell specially.  We
should just fold it into the next paragraph:

254 Commands and Utilities

     Default install of any compliant system shall provide commands and
     utilities described the the package list of the MeeGo reference
     implementation.

This ought to be able to cover the shell as well.  Then we just need to
choose a shell that is acceptable to everyone, which might not be bash
(because of its license).
Since many packages include shell scripts for pre- or post-inst
operations, or even for run-time set-up, it seems reasonable to define
some kind of subset of commands and some version of a standard shell.
Without going overboard, of course.

Similarly for scripting languages, if you're writing a Python app it's
important to know that Python 2.7.x won't be on any MeeGo device.

why wouldn't it be? Maybe not for 1.1.. but for 1.2 ?

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to