mycroft-core/dev_setup.sh

296 lines
10 KiB
Bash
Raw Normal View History

In the 1970s computer users had to understand the arcane syntax of the machines they used. They programed their computers using the machine's native language and hardly gave it a thought. The 1980s birthed a new form of interaction between computers and users. For the first time computers became capable of understanding the most basic form of human communication - pointing and grunting. The mouse and the GUI revolutionized computing and made computers accessible to the masses. We have now entered a third era. We are rapidly approaching a time when computer systems will understand human language and respond using the most natural form of human communication – speech. This is an important development. Some might even call it revolutionary. Despite its importance, however, the technologies that will underpin this new method of interaction are the property of major tech firms who don't necessarily have the public's best interests at heart. Not anymore. Meet Mycroft – the worlds first open source natural language platform. Mycroft understands human language and responds with speech. It is being designed to run on anything from a phone to an automobile and will change the way we interact with open source technologies in profound ways. Our goal here at Mycroft is to improve this technology to the point that when you interact with the software it is impossible to tell if you are talking to a human or a machine. This initial release of the Mycroft software represents a significant effort by the Mycroft community to give the open source world access to this important technology. We are all hoping that the software will be useful to the public and will help to usher in a new era of human machine interaction. Our community welcomes everyone to use Mycroft, improve the software and contribute back to the project. With your help and support we can truly make Mycroft an AI for everyone. Joshua W Montgomery – May 17, 2016
2016-05-20 14:16:01 +00:00
#!/usr/bin/env bash
Change to Apache 2.0 license from GPLv3.0 This commit officially switches the mycroft-core repository from GPLv3.0 licensing to Apache 2.0. All dependencies on GPL'ed code have been removed and we have contacted all previous contributors with still-existing code in the repository to agree to this change. Going forward, all contributors will sign a Contributor License Agreement (CLA) by visiting https://mycroft.ai/cla, then they will be included in the Mycroft Project's overall Contributor list, found at: https://github.com/MycroftAI/contributors. This cleanly protects the project, the contributor and all who use the technology to build upon. Futher discussion can be found at this blog post: https://mycroft.ai/blog/right-license/ This commit also removes all __author__="" from the code. These lines are painful to maintain and the etiquette surrounding their maintainence is unclear. Do you remove a name from the list if the last line of code the wrote gets replaced? Etc. Now all contributors are publicly acknowledged in the aforementioned repo, and actual authorship is maintained by Github in a much more effective and elegant way! Finally, a few references to "Mycroft AI" were changed to the correct legal entity name "Mycroft AI Inc." ==== Fixed Issues ==== #403 Update License.md and file headers to Apache 2.0 #400 Update LICENSE.md ==== Documentation Notes ==== Deprecated the ScheduledSkill and ScheduledCRUDSkill classes. These capabilities have been superceded by the more flexible MycroftSkill class methods schedule_event(), schedule_repeating_event(), update_event(), and cancel_event().
2017-10-04 06:28:44 +00:00
# Copyright 2017 Mycroft AI Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
######################################################
# @author sean.fitzgerald (aka clusterfudge)
#
# The purpose of this script is to create a self-
# contained development environment using
# virtualenv for python dependency sandboxing.
# This script will create a virtualenv (using the
# conventions set by virtualenv-wrapper for
# location and naming) and install the requirements
# laid out in requirements.txt, pocketsphinx, and
# pygtk into the virtualenv. Mimic will be
# installed and built from source inside the local
# checkout.
#
# The goal of this script is to create a development
# environment in user space that is fully functional.
# It is expected (and even encouraged) for a developer
# to work on multiple projects concurrently, and a
# good OSS citizen respects that and does not pollute
# a developers workspace with it's own dependencies
# (as much as possible).
# </endRant>
######################################################
In the 1970s computer users had to understand the arcane syntax of the machines they used. They programed their computers using the machine's native language and hardly gave it a thought. The 1980s birthed a new form of interaction between computers and users. For the first time computers became capable of understanding the most basic form of human communication - pointing and grunting. The mouse and the GUI revolutionized computing and made computers accessible to the masses. We have now entered a third era. We are rapidly approaching a time when computer systems will understand human language and respond using the most natural form of human communication – speech. This is an important development. Some might even call it revolutionary. Despite its importance, however, the technologies that will underpin this new method of interaction are the property of major tech firms who don't necessarily have the public's best interests at heart. Not anymore. Meet Mycroft – the worlds first open source natural language platform. Mycroft understands human language and responds with speech. It is being designed to run on anything from a phone to an automobile and will change the way we interact with open source technologies in profound ways. Our goal here at Mycroft is to improve this technology to the point that when you interact with the software it is impossible to tell if you are talking to a human or a machine. This initial release of the Mycroft software represents a significant effort by the Mycroft community to give the open source world access to this important technology. We are all hoping that the software will be useful to the public and will help to usher in a new era of human machine interaction. Our community welcomes everyone to use Mycroft, improve the software and contribute back to the project. With your help and support we can truly make Mycroft an AI for everyone. Joshua W Montgomery – May 17, 2016
2016-05-20 14:16:01 +00:00
# exit on any error
set -Ee
cd $(dirname $0)
TOP=$( pwd -L )
function show_help() {
echo "dev_setup.sh: Mycroft development environment setup"
echo "Usage: dev_setup.sh [options]"
echo
echo "Options:"
echo " -r, --allow-root Allow to be run as root (e.g. sudo)"
echo " -fm Force mimic build"
echo " -h, --help Show this message"
echo
echo "This will prepare your environment for running the mycroft-core"
echo "services. Normally this should be run as a normal user,"
echo "not as root/sudo."
}
opt_forcemimicbuild=false
opt_allowroot=false
for var in "$@" ; do
if [[ ${var} == "-h" ]] || [[ ${var} == "--help" ]] ; then
show_help
exit 0
fi
if [[ ${var} == "-r" ]] || [[ ${var} == "--allow-root" ]] ; then
opt_allowroot=true
fi
if [[ ${var} == "-fm" ]] ; then
opt_forcemimicbuild=true
fi
done
if [ $(id -u) -eq 0 ] && [ "${opt_allowroot}" != true ] ; then
echo "This script should not be run as root or with sudo."
echo "To force, rerun with --allow-root"
exit 1
fi
Unify the command line experience across platforms (#1784) * Unify the command line experience across platforms Interacting with Mycroft was slightly different on different platforms (Mark 1, Github, Picroft), which resulted in confusion and the beginnings of a documentation/support nightmare. This moves several of the common commands into a mycroft-core/bin folder instead of being build in packaging or part of the Picroft package only. This required a small changes to the common scripts, in addition to adding the new scripts. Here are details: * dev_setup.sh - Stubbed out a setup wizard (TODO) - Jumped to latest version of pip (18.0) - Set execution flags for new scripts * start-mycroft.sh - Allow auto-execution of dev_setup.sh - De-sourced the stop-mycroft.sh calls (not needed) - Add quotes to better handle paths with spaces * stop-mycroft.sh - Return exit code to show if a service was stopped or killed - Extend the time to wait for a gently shutdown from 2 secs to 5 - Changed to say "messagebus.service" instead of just "service" to be more clear (the name "service" means nothing to users, but "bus does") * venv-activate.sh - Added help - Added -q or --quiet mode - Added toggled availability of 'mycroft-venv-activate' and 'mycroft-venv-deactivate' aliases. Only one is available at any given time. New scripts: * mycroft-cli-client: start up the CLI * mycroft-help: shows hints on using mycroft * mycroft-mic-test: runs the basic record/playback, playing nicely with a running Mycroft by stopping and restarting services as appropriate * mycroft-pip: manage the venv via pip * mycroft-say-to: send utterances, like a user spoke them * mycroft-speak: speaks the given phrase using Mycroft * mycroft-skill-testrunner: invoke the single-skill test runner All of these scripts are easy to discover by typing "mycroft-" then hitting the TAB key. ==== INSTALLER NOTES ==== * We no longer need to create mycroft-cli-client and mycroft-pip in the Debian packages. * mycroft-core/bin should be added to the path * Corrections after review Several minor corrections, plus added wrappers for the 'msm' and 'msk' utilities. * Set executable flag on script files in bin/ The scripts in the bin/ folder needed to be changed to executable within git to prevent looking dirty after dev_setup.sh has been run. * Add executable flag to one more script
2018-09-09 21:55:01 +00:00
# TODO: Create a setup wizard that guides the user through some decisions
# if [ ! -f .dev_opts.json ] ; then
# E.g.:
# * Run on 'master' or on 'dev'? Most users probably want 'master'
# * Auto-update? When on, it will pull and run dev_setup automatically
# * Pull down mimic source? Most will be happy with just the package
# * Add mycroft-core/bin to the .bashrc PATH?
# from Picroft's wizard:
# echo '{"use_branch":"master", "auto_update": true}' > .dev_opts.json
# or
# echo '{"use_branch":"dev", "auto_update": false}' > .dev_opts.json
# fi
function os_is() {
[[ $(grep "^ID=" /etc/os-release | awk -F'=' '/^ID/ {print $2}' | sed 's/\"//g') == $1 ]]
}
function found_exe() {
hash "$1" 2>/dev/null
}
function install_deps() {
echo "Installing packages..."
if found_exe sudo ; then
SUDO=sudo
else
echo "This script requires \"sudo\" to install system packages. Please install it, then re-run this script."
exit 1
fi
if found_exe zypper ; then
# OpenSUSE
$SUDO zypper install -y git python3 python3-devel libtool libffi-devel libopenssl-devel autoconf automake bison swig portaudio-devel mpg123 flac curl libicu-devel pkg-config libjpeg-devel libfann-devel python3-curses pulseaudio
Unify the command line experience across platforms (#1784) * Unify the command line experience across platforms Interacting with Mycroft was slightly different on different platforms (Mark 1, Github, Picroft), which resulted in confusion and the beginnings of a documentation/support nightmare. This moves several of the common commands into a mycroft-core/bin folder instead of being build in packaging or part of the Picroft package only. This required a small changes to the common scripts, in addition to adding the new scripts. Here are details: * dev_setup.sh - Stubbed out a setup wizard (TODO) - Jumped to latest version of pip (18.0) - Set execution flags for new scripts * start-mycroft.sh - Allow auto-execution of dev_setup.sh - De-sourced the stop-mycroft.sh calls (not needed) - Add quotes to better handle paths with spaces * stop-mycroft.sh - Return exit code to show if a service was stopped or killed - Extend the time to wait for a gently shutdown from 2 secs to 5 - Changed to say "messagebus.service" instead of just "service" to be more clear (the name "service" means nothing to users, but "bus does") * venv-activate.sh - Added help - Added -q or --quiet mode - Added toggled availability of 'mycroft-venv-activate' and 'mycroft-venv-deactivate' aliases. Only one is available at any given time. New scripts: * mycroft-cli-client: start up the CLI * mycroft-help: shows hints on using mycroft * mycroft-mic-test: runs the basic record/playback, playing nicely with a running Mycroft by stopping and restarting services as appropriate * mycroft-pip: manage the venv via pip * mycroft-say-to: send utterances, like a user spoke them * mycroft-speak: speaks the given phrase using Mycroft * mycroft-skill-testrunner: invoke the single-skill test runner All of these scripts are easy to discover by typing "mycroft-" then hitting the TAB key. ==== INSTALLER NOTES ==== * We no longer need to create mycroft-cli-client and mycroft-pip in the Debian packages. * mycroft-core/bin should be added to the path * Corrections after review Several minor corrections, plus added wrappers for the 'msm' and 'msk' utilities. * Set executable flag on script files in bin/ The scripts in the bin/ folder needed to be changed to executable within git to prevent looking dirty after dev_setup.sh has been run. * Add executable flag to one more script
2018-09-09 21:55:01 +00:00
$SUDO zypper install -y -t pattern devel_C_C++
elif found_exe yum && os_is centos ; then
# CentOS
2018-10-08 16:19:30 +00:00
$SUDO yum install epel-release
$SUDO yum install -y cmake gcc-c++ git python34 python34-devel libtool libffi-devel openssl-devel autoconf automake bison swig portaudio-devel mpg123 flac curl libicu-devel python34-pkgconfig libjpeg-devel fann-devel python34-libs pulseaudio
git clone https://github.com/libfann/fann.git
cd fann
git checkout b211dc3db3a6a2540a34fbe8995bf2df63fc9939
2018-10-08 16:19:30 +00:00
cmake .
$SUDO make install
cd "${TOP}"
rm -rf fann
elif found_exe apt-get ; then
# Debian / Ubuntu
2018-05-11 20:44:42 +00:00
$SUDO apt-get install -y git python3 python3-dev python-setuptools python-gobject-2-dev libtool libffi-dev libssl-dev autoconf automake bison swig libglib2.0-dev portaudio19-dev mpg123 screen flac curl libicu-dev pkg-config automake libjpeg-dev libfann-dev build-essential jq
elif found_exe pacman; then
# Arch Linux
$SUDO pacman -S --needed --noconfirm git python python-pip python-setuptools python-virtualenv python-gobject python-virtualenvwrapper libffi swig portaudio mpg123 screen flac curl icu libjpeg-turbo base-devel jq pulseaudio pulseaudio-alsa
pacman -Qs "^fann$" &> /dev/null || (
git clone https://aur.archlinux.org/fann.git
cd fann
makepkg -srciA --noconfirm
cd ..
rm -rf fann
)
elif found_exe dnf ; then
# Fedora
$SUDO dnf install -y git python3 python3-devel python3-pip python3-setuptools python3-virtualenv pygobject3-devel libtool libffi-devel openssl-devel autoconf bison swig glib2-devel portaudio-devel mpg123 mpg123-plugins-pulseaudio screen curl pkgconfig libicu-devel automake libjpeg-turbo-devel fann-devel gcc-c++ redhat-rpm-config jq
else
if found_exe tput ; then
green="$(tput setaf 2)"
blue="$(tput setaf 4)"
reset="$(tput sgr0)"
fi
echo
echo "${green}Could not find package manager"
echo "${green}Make sure to manually install:${blue} git python 2 python-setuptools python-virtualenv pygobject virtualenvwrapper libtool libffi openssl autoconf bison swig glib2.0 portaudio19 mpg123 flac curl fann g++"
echo $reset
fi
}
VIRTUALENV_ROOT=${VIRTUALENV_ROOT:-"${TOP}/.venv"}
function install_venv() {
2018-04-27 14:12:17 +00:00
python3 -m venv "${VIRTUALENV_ROOT}/" --without-pip
# Force version of pip for reproducability, but there is nothing special
# about this version. Update whenever a new version is released and
# verified functional.
curl https://bootstrap.pypa.io/3.3/get-pip.py | "${VIRTUALENV_ROOT}/bin/python" - 'pip==18.0.0'
}
install_deps
# Configure to use the standard commit template for
# this repo only.
git config commit.template .gitmessage
# Check whether to build mimic (it takes a really long time!)
build_mimic="n"
if [[ ${opt_forcemimicbuild} == true ]] ; then
build_mimic="y"
else
# first, look for a build of mimic in the folder
has_mimic=""
if [[ -f ${TOP}/mimic/bin/mimic ]] ; then
has_mimic=$( ${TOP}/mimic/bin/mimic -lv | grep Voice ) || true
fi
# in not, check the system path
if [ "$has_mimic" == "" ] ; then
if [ -x "$(command -v mimic)" ] ; then
has_mimic="$( mimic -lv | grep Voice )" || true
fi
fi
if [ "$has_mimic" == "" ]; then
build_mimic="y"
fi
fi
if [ ! -x "${VIRTUALENV_ROOT}/bin/activate" ] ; then
install_venv
In the 1970s computer users had to understand the arcane syntax of the machines they used. They programed their computers using the machine's native language and hardly gave it a thought. The 1980s birthed a new form of interaction between computers and users. For the first time computers became capable of understanding the most basic form of human communication - pointing and grunting. The mouse and the GUI revolutionized computing and made computers accessible to the masses. We have now entered a third era. We are rapidly approaching a time when computer systems will understand human language and respond using the most natural form of human communication – speech. This is an important development. Some might even call it revolutionary. Despite its importance, however, the technologies that will underpin this new method of interaction are the property of major tech firms who don't necessarily have the public's best interests at heart. Not anymore. Meet Mycroft – the worlds first open source natural language platform. Mycroft understands human language and responds with speech. It is being designed to run on anything from a phone to an automobile and will change the way we interact with open source technologies in profound ways. Our goal here at Mycroft is to improve this technology to the point that when you interact with the software it is impossible to tell if you are talking to a human or a machine. This initial release of the Mycroft software represents a significant effort by the Mycroft community to give the open source world access to this important technology. We are all hoping that the software will be useful to the public and will help to usher in a new era of human machine interaction. Our community welcomes everyone to use Mycroft, improve the software and contribute back to the project. With your help and support we can truly make Mycroft an AI for everyone. Joshua W Montgomery – May 17, 2016
2016-05-20 14:16:01 +00:00
fi
# Start the virtual environment
2017-06-13 19:50:44 +00:00
source "${VIRTUALENV_ROOT}/bin/activate"
cd "${TOP}"
PYTHON=$( python -c "import sys;print('python{}.{}'.format(sys.version_info[0], sys.version_info[1]))" )
In the 1970s computer users had to understand the arcane syntax of the machines they used. They programed their computers using the machine's native language and hardly gave it a thought. The 1980s birthed a new form of interaction between computers and users. For the first time computers became capable of understanding the most basic form of human communication - pointing and grunting. The mouse and the GUI revolutionized computing and made computers accessible to the masses. We have now entered a third era. We are rapidly approaching a time when computer systems will understand human language and respond using the most natural form of human communication – speech. This is an important development. Some might even call it revolutionary. Despite its importance, however, the technologies that will underpin this new method of interaction are the property of major tech firms who don't necessarily have the public's best interests at heart. Not anymore. Meet Mycroft – the worlds first open source natural language platform. Mycroft understands human language and responds with speech. It is being designed to run on anything from a phone to an automobile and will change the way we interact with open source technologies in profound ways. Our goal here at Mycroft is to improve this technology to the point that when you interact with the software it is impossible to tell if you are talking to a human or a machine. This initial release of the Mycroft software represents a significant effort by the Mycroft community to give the open source world access to this important technology. We are all hoping that the software will be useful to the public and will help to usher in a new era of human machine interaction. Our community welcomes everyone to use Mycroft, improve the software and contribute back to the project. With your help and support we can truly make Mycroft an AI for everyone. Joshua W Montgomery – May 17, 2016
2016-05-20 14:16:01 +00:00
# Add mycroft-core to the virtualenv path
# (This is equivalent to typing 'add2virtualenv $TOP', except
# you can't invoke that shell function from inside a script)
VENV_PATH_FILE="${VIRTUALENV_ROOT}/lib/$PYTHON/site-packages/_virtualenv_path_extensions.pth"
if [ ! -f "$VENV_PATH_FILE" ] ; then
echo "import sys; sys.__plen = len(sys.path)" > "$VENV_PATH_FILE" || return 1
echo "import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new)" >> "$VENV_PATH_FILE" || return 1
fi
if ! grep -q "$TOP" $VENV_PATH_FILE ; then
echo "Adding mycroft-core to virtualenv path"
sed -i.tmp '1 a\
'"$TOP"'
' "${VENV_PATH_FILE}"
fi
# install required python modules
if ! pip install -r requirements.txt ; then
echo "Warning: Failed to install all requirements. Continue? y/N"
read -n1 continue
if [[ "$continue" != "y" ]] ; then
exit 1
fi
fi
In the 1970s computer users had to understand the arcane syntax of the machines they used. They programed their computers using the machine's native language and hardly gave it a thought. The 1980s birthed a new form of interaction between computers and users. For the first time computers became capable of understanding the most basic form of human communication - pointing and grunting. The mouse and the GUI revolutionized computing and made computers accessible to the masses. We have now entered a third era. We are rapidly approaching a time when computer systems will understand human language and respond using the most natural form of human communication – speech. This is an important development. Some might even call it revolutionary. Despite its importance, however, the technologies that will underpin this new method of interaction are the property of major tech firms who don't necessarily have the public's best interests at heart. Not anymore. Meet Mycroft – the worlds first open source natural language platform. Mycroft understands human language and responds with speech. It is being designed to run on anything from a phone to an automobile and will change the way we interact with open source technologies in profound ways. Our goal here at Mycroft is to improve this technology to the point that when you interact with the software it is impossible to tell if you are talking to a human or a machine. This initial release of the Mycroft software represents a significant effort by the Mycroft community to give the open source world access to this important technology. We are all hoping that the software will be useful to the public and will help to usher in a new era of human machine interaction. Our community welcomes everyone to use Mycroft, improve the software and contribute back to the project. With your help and support we can truly make Mycroft an AI for everyone. Joshua W Montgomery – May 17, 2016
2016-05-20 14:16:01 +00:00
if ! pip install -r test-requirements.txt ; then
echo "Warning test requirements wasn't installed, Note: normal operation should still work fine..."
2018-05-21 13:51:08 +00:00
fi
SYSMEM=$( free | awk '/^Mem:/ { print $2 }' )
MAXCORES=$(($SYSMEM / 512000))
MINCORES=1
CORES=$( nproc )
# ensure MAXCORES is > 0
if [[ ${MAXCORES} -lt 1 ]] ; then
MAXCORES=${MINCORES}
fi
# look for positive integer
if ! [[ ${CORES} =~ ^[0-9]+$ ]] ; then
CORES=${MINCORES}
elif [[ ${MAXCORES} -lt ${CORES} ]] ; then
CORES=${MAXCORES}
2017-06-13 19:50:44 +00:00
fi
2017-06-13 19:50:44 +00:00
echo "Building with $CORES cores."
2016-07-29 19:50:38 +00:00
#build and install pocketsphinx
#cd ${TOP}
#${TOP}/scripts/install-pocketsphinx.sh -q
#build and install mimic
2017-06-13 19:50:44 +00:00
cd "${TOP}"
if [[ "$build_mimic" == "y" ]] || [[ "$build_mimic" == "Y" ]] ; then
echo "WARNING: The following can take a long time to run!"
"${TOP}/scripts/install-mimic.sh" " ${CORES}"
else
echo "Skipping mimic build."
fi
2016-06-23 15:29:11 +00:00
# set permissions for common scripts
chmod +x start-mycroft.sh
chmod +x stop-mycroft.sh
Unify the command line experience across platforms (#1784) * Unify the command line experience across platforms Interacting with Mycroft was slightly different on different platforms (Mark 1, Github, Picroft), which resulted in confusion and the beginnings of a documentation/support nightmare. This moves several of the common commands into a mycroft-core/bin folder instead of being build in packaging or part of the Picroft package only. This required a small changes to the common scripts, in addition to adding the new scripts. Here are details: * dev_setup.sh - Stubbed out a setup wizard (TODO) - Jumped to latest version of pip (18.0) - Set execution flags for new scripts * start-mycroft.sh - Allow auto-execution of dev_setup.sh - De-sourced the stop-mycroft.sh calls (not needed) - Add quotes to better handle paths with spaces * stop-mycroft.sh - Return exit code to show if a service was stopped or killed - Extend the time to wait for a gently shutdown from 2 secs to 5 - Changed to say "messagebus.service" instead of just "service" to be more clear (the name "service" means nothing to users, but "bus does") * venv-activate.sh - Added help - Added -q or --quiet mode - Added toggled availability of 'mycroft-venv-activate' and 'mycroft-venv-deactivate' aliases. Only one is available at any given time. New scripts: * mycroft-cli-client: start up the CLI * mycroft-help: shows hints on using mycroft * mycroft-mic-test: runs the basic record/playback, playing nicely with a running Mycroft by stopping and restarting services as appropriate * mycroft-pip: manage the venv via pip * mycroft-say-to: send utterances, like a user spoke them * mycroft-speak: speaks the given phrase using Mycroft * mycroft-skill-testrunner: invoke the single-skill test runner All of these scripts are easy to discover by typing "mycroft-" then hitting the TAB key. ==== INSTALLER NOTES ==== * We no longer need to create mycroft-cli-client and mycroft-pip in the Debian packages. * mycroft-core/bin should be added to the path * Corrections after review Several minor corrections, plus added wrappers for the 'msm' and 'msk' utilities. * Set executable flag on script files in bin/ The scripts in the bin/ folder needed to be changed to executable within git to prevent looking dirty after dev_setup.sh has been run. * Add executable flag to one more script
2018-09-09 21:55:01 +00:00
chmod +x bin/mycroft-cli-client
chmod +x bin/mycroft-help
chmod +x bin/mycroft-mic-test
chmod +x bin/mycroft-msk
chmod +x bin/mycroft-msm
chmod +x bin/mycroft-pip
chmod +x bin/mycroft-say-to
chmod +x bin/mycroft-skill-testrunner
chmod +x bin/mycroft-speak
# create and set permissions for logging
if [[ ! -w /var/log/mycroft/ ]] ; then
# Creating and setting permissions
echo "Creating /var/log/mycroft/ directory"
if [[ ! -d /var/log/mycroft/ ]] ; then
sudo mkdir /var/log/mycroft/
fi
sudo chmod 777 /var/log/mycroft/
fi
#Store a fingerprint of setup
md5sum requirements.txt test-requirements.txt dev_setup.sh > .installed