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:
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 OSF1
dh_installmenu
DH_INSTALLMENU(1) Debhelper DH_INSTALLMENU(1)NAME
dh_installmenu - install Debian menu files into package build directories
SYNOPSIS
dh_installmenu [debhelperoptions] [-n]
DESCRIPTION
dh_installmenu is a debhelper program that is responsible for installing files used by the Debian menu package into package build
directories.
It also automatically generates the postinst and postrm commands needed to interface with the Debian menu package. These commands are
inserted into the maintainer scripts by dh_installdeb(1).
FILES
debian/package.menu
Debian menu files, installed into usr/share/menu/package in the package build directory. See menufile(5) for its format.
debian/package.menu-method
Debian menu method files, installed into etc/menu-methods/package in the package build directory.
OPTIONS -n, --no-scripts
Do not modify postinst/postrm scripts.
SEE ALSO debhelper(7)update-menus(1)menufile(5)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_INSTALLMENU(1)