Sponsored Content
Top Forums UNIX for Advanced & Expert Users Creating Installer and/or Package Post 302935686 by sea on Wednesday 18th of February 2015 02:12:06 PM
Old 02-18-2015
Make yourself clear on your projects range.
Its not a simple 30 line script.

It will become complex, thus it is an application, thus it should be 'installed' properly.
By that i mean, use your system default paths to place your application pieces.

Examples: (valid for redhat based distros)
The start binary (or script) to /usr/bin/cplm
Your other cplm files to /usr/share/cplm
Your manpages should go to something like: /usr/share/man/man1/cplm.1
Your bash completition to /etc/bash_completion.d/

Also, make sure the installation process works without removing the original data, so you can run your install script straight from your projects folder, overwriting the installed data -> so you always use the installed version - NOT the version you working on.

If it was a single file, using a single configuration file, it could be made running from anywhere one wants, but i doubt you can limit this project to a single execution and a single config file only.
And to get started, as a first approach - make your install script work for you.
You cant expect people to run an incomplete application, so for the time beeing you're currently the only one using the installation script, until it reaches some kind of quality, and by that time, you'll know enough to improve the install script to work for others as well.

Hope this helps
This User Gave Thanks to sea For This Post:
 

8 More Discussions You Might Find Interesting

1. Linux

how to restore original package after uninstalling the upgraded package using rpm

have following package installed rpm -qa |grep ADMIN It will give the following package installed: ADMIN-4.0.0.1 Now I will upgrade the ADMIN package using the following command. rpm --upgrade ADMIN-4.1.0.1 It will upgrade the ADMIN packagge to ADMIN-4.1.0.1 Now I want that... (0 Replies)
Discussion started by: amitpansuria
0 Replies

2. Solaris

Design for development of solaris package (installer)

Hi, I am new to solaris. As I am assigned to a new task to develop a installer for an application on solaris10 machine, I need to prepare the design document for the installer. ( I came to know that in solaris all the instllables will be considered as packages and and are not like .exe's). So... (0 Replies)
Discussion started by: raghu.amilineni
0 Replies

3. Ubuntu

Problem creating Desktop shortcuts through Debian dpkg installer scripts

Hi, I am creating a debian package (*.deb) for my application using the command I am using debian pre/post installer scripts to do certain tasks before/after installation/uninstallation. One such task is to create a shortcut on the user's desktop to launch my application. I am trying to do this... (0 Replies)
Discussion started by: royalibrahim
0 Replies

4. AIX

mkinstallp package creation failing "no such file: ./usr/lpp/<package name>/inst_root"

Hello, I'm trying to build a (bff) package from an already installed program (clam antivirus) using mkinstallp. However, mkinstallp fails with "no such file: ./usr/lpp/<package name>/inst_root" I'm not sure why all files get created ok except for these particular ones. Any help would be... (2 Replies)
Discussion started by: omonte
2 Replies

5. UNIX for Advanced & Expert Users

How to find dependancies of .dstream package (Solaris) & .rpm package( linux)

Friends, Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ? For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies

6. Red Hat

Creating rpm package file

Hi, I have a binary file ans some scripts which copy the binary file to a location and create some files and then add a entry to cron . I want to create a rpm package file for all these.So that if a user run: rpm -i my.rpm the binary is copied and scripts are run. Can anyone help me in... (1 Reply)
Discussion started by: kailash19
1 Replies

7. UNIX for Dummies Questions & Answers

Can't install rpm package with --prefix in new path.Error: package is not relocatable

Hello, i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm" in /usr/local/ directory. I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't. I did: 1st try: Didn't work sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies

8. Emergency UNIX and Linux Support

Problem when trying to remove a package using rpm command - error: package is not installed

Hello, i have installed a package by using the command sudo rpm -i filepackage.rpm package filepackage is already installed when i try to remove it, i get an error saying "is not installed": sudo rpm -e filepackage.rpm error: package filepackage is not installed How can... (4 Replies)
Discussion started by: g_p
4 Replies
GIMPTOOL-2.0(1) 					      General Commands Manual						   GIMPTOOL-2.0(1)

NAME
gimptool-2.0 - script to perform various GIMPy functions SYNOPSIS
gimptool-2.0 [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--msvc-syntax] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--unin- stall-admin-script script.scm] DESCRIPTION
gimptool-2.0 is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool-2.0 can also be used by programs that need to know what libraries and include-paths GIMP was compiled with. gimptool-2.0 uses pkg- config for this task. For use in Makefiles, it is recommended that you use pkg-config directly instead of calling gimptool-2.0. OPTIONS
gimptool-2.0 accepts the following options: --version Print the currently installed version of GIMP on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but don't actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but don't actually execute them. Same as -n. --dry-run Test mode. Print the commands but don't actually execute them. Same as -n. --recon Test mode. Print the commands but don't actually execute them. Same as -n. --msvc-syntax Useful on Windows. Outputs the compiler and linker flags in the syntax used by Microsoft's toolchain. Passed to the pkg-config com- mand that does most of gimptool-2.0's work. --bindir Outputs the bindir used to install the GIMP. --sbindir Outputs the sbindir used to install the GIMP. --libexecdir Outputs the libexecdir used to install the GIMP. --datadir Outputs the datadir used to install the GIMP. --sysconfdir Outputs the sysconfdir used to install the GIMP. --sharedstatedir Outputs the sharedstatedir used to install the GIMP. --localstatedir Outputs the localstatedir used to install the GIMP. --libdir Outputs the libdir used to install the GIMP. --infodir Outputs the infodir used to install the GIMP. --mandir Outputs the mandir used to install the GIMP. --includedir Outputs the includedir used to install the GIMP. --gimpdatadir Outputs the actual directory where the GIMP data files were installed. --gimpplugindir Outputs the actual directory where the GIMP plug-ins were installed. --build plug-in.c Compile and link plug-in.c into a GIMP plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a GIMP plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin plug-in Install plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-script script.scm Install script.scm into the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --install-admin-script script.scm Install script.scm into the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --libs Print the linker flags that are necessary to link a GIMP plug-in. --libs-noui Print the linker flags that are necessary to link a GIMP plug-in, for plug-ins that do not require the GTK+ libraries. --cflags Print the compiler flags that are necessary to compile a GIMP plug-in. --clags-noui Print the compiler flags that are necessary to compile a GIMP plug-in for plug-ins that do not require the GTK+ libraries. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. LDFLAGS to get the preferred flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . PKG_CONFIG to get the location of the pkg-config program that is used to determine details about your glib, pango, gtk+ and gimp installation. SEE ALSO
gimp(1), gimprc(5), pkg-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and is based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). GIMP Manual Pages Version 2.8.10 GIMPTOOL-2.0(1)
All times are GMT -4. The time now is 02:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy