The only tasks that need to be performed for installation are 1) unzip the package, 2) modify the user's ~/.bashrc config file, and 3) make the scripts executable.
I have written an install script that will accomplish steps 2 and 3. However, users still have to unzip the package, make the install script executable, and execute the install script. This seems a bit sloppy to me.
Make it a tar, cpio, or other kind of UNIX archive instead of a zip. Permissions are preserved in those, including executable bits.
Include an installer script, like so:
Code:
#!/bin/bash
if grep -q "###APPNAME###" ~/.bashrc
then
echo "Application is already installed in your bashrc"
exit 1
fi
cat >>~/.bashrc <<EOF
/path/to/application ###APPNAME###
EOF
echo "Application now installed in your bashrc!"
Have users run it from shell. Two steps instead of one, to be sure, but sysadmins will thank you for a package which doesn't mangle login scripts unless asked.
Hi
I'm well worsed in Shell Scripting on UNIX OS. But I found the script used in Make file for compiling the unix sources is quite criptic. Even though it looks some what like any other Shell Script, but I noticed lots of difference & I'm always facing difficult in understanding the code... (5 Replies)
Hi there,
I am installing a package at the moment on to my Solaris version 8 and I have run into a problem with the 'make' command. I have installed the package using the 'pkgadd' command and I am now at the stage where I have to use the 'make' command followed by the 'make install'... (4 Replies)
Hello
is there any way to if lets say i have main.pl script , but i have 3 includes in this perl script
now i will like to some how to treat this main.pl and its includes files as single file
something like -E (Preprocess only; do not compile, assemble or link) in the c compilers .
in short i... (0 Replies)
Hi,
Recently I install a package and try to do a make and make install.
However, in the make it gives me below error:-
make:Nothing to be done for 'install-exec-am'
make:Nothing to be done for 'install-data-am'
Can anyone please explain to me what does this mean? I have been trying... (1 Reply)
I attached a README file that I will refer to.
I successfully completed everything in the README file until step 4.
# pwd
/gani/gani-2.4.4
# ls
COPYING Makefile.macros gem.c
Makefile Makefile.sparc_gcc gem.h
Makefile.amd64_gcc ... (1 Reply)
Hi,
While installation of apache on linux, we perform the below tasks.
1) Untar
2) configure
3) make
4) make install.
I wanted to understand the difference and working of configure/make/make install.
Can any one help me understanding this?
Thanks in advance. (1 Reply)
Hi all,
Just writing to ask if any one can advise on what tools to use best for maintaining your scripts ... preferably free/open source and portable if there is one, that is, one that can be placed and run on a USB stick ...
At the moment, am having them in directories and files and no... (2 Replies)
Hello. This is what I get when I try to install
Todd-Sheppards-Computer:~/make-3.82 toddsheppard$ sudo make install
Password:
Making install in glob
make: Nothing to be done for `install-exec-am'.
make: Nothing to be done for `install-data-am'.
Making install in config
make: Nothing to be... (3 Replies)
Hello Everyone,
I want to know how can we make the variables of one script available for the other script?
for example i have three scripts variable_availability.sh,first.sh,second.sh and a file containing variables called common
----------------------------------
cat variable_availability.sh... (2 Replies)
hi dear
i want to know what is different between make check install and make all install?
thanks in advane
fereshte (3 Replies)
Discussion started by: komijani
3 Replies
LEARN ABOUT LINUX
npm-run-script
NPM-RUN-SCRIPT(1)NPM-RUN-SCRIPT(1)NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)