On 08/19/2010 02:08 PM, Jason Kridner wrote:
If nano is available and EDITOR isn't otherwise set, then use it.
Advanced users who would prefer vi will know how to set EDITOR anyway.
I can clearly see myself being frustrated typing 'export EDITOR=vi'
every time I start a BeagleBoard test ramdisk image, but better me have
that than to try to explain to someone fresh how to use vi.
Signed-off-by: Jason Kridner<[email protected]>
---
recipes/base-files/base-files/beagleboard/profile | 41 +++++++++++++++++++++
1 files changed, 41 insertions(+), 0 deletions(-)
create mode 100644 recipes/base-files/base-files/beagleboard/profile
diff --git a/recipes/base-files/base-files/beagleboard/profile
b/recipes/base-files/base-files/beagleboard/profile
new file mode 100644
index 0000000..7b1cf52
--- /dev/null
+++ b/recipes/base-files/base-files/beagleboard/profile
@@ -0,0 +1,41 @@
+# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
+# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
+
+PATH="/usr/local/bin:/usr/bin:/bin"
+# EDITOR needed for packages like cron
+if [ "$EDITOR" ]; then
You sure you don't want this test instead?
if [ -z "$EDITOR" ]; then
Otherwise, you'll be overriding some guy's choice and never defining
it for those who haven't
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
