Sponsored Content
Full Discussion: Wanted: Feedback on TUI
The Lounge What is on Your Mind? Wanted: Feedback on TUI Post 302935712 by sea on Wednesday 18th of February 2015 05:05:48 PM
Old 02-18-2015
Thank you Corona.
That is one of the points why i'm asking, on RedHat based systems, these paths are the system defaults and are used by the packaging system (rpm) too.

Might i ask what system you are using / did install TUI on?

Note to self:
Need to store the PREFIX from within the installation script, and reuse it for those installed command rely on "/usr/share/$app/*".
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Feedback on Script.

Hi all, Would like to get some feedback on a scrip that I've finished writing at home for work. Any constructive feedback from operations used to legibility, etc. would be appreciated - anything at all. It's my first real script that will be running on a clients server. The script is... (2 Replies)
Discussion started by: Cameron
2 Replies

2. UNIX for Dummies Questions & Answers

feedback form ?! :-(

hi, i am VERY new to UNIX. just wanted some help on a feedback form that i have hosted on a unix server. the feedback form is in asp and doesnt work on unix. any other language to get it working ?? HELP !!! (3 Replies)
Discussion started by: shahenil
3 Replies

3. Programming

Feedback algorithm

Hi I search an exemple of scheduling Feedback algorithm, or help about how to create one. Thanks (0 Replies)
Discussion started by: messier79
0 Replies

4. Shell Programming and Scripting

kshdb feedback

Hi I'm looking for some feedback on kshdb, what are peoples general feeling about it etc. Also has anyone used this as a test mechanism? I am thinking about trying to wrap a basic test script around this. (0 Replies)
Discussion started by: eeisken
0 Replies

5. HP-UX

Start SAM in TUI from CDE session

how can i start sam in TUI mode from a CDE session. i'm using hp-ux 11iv3 i tried to start SAM from a terminal from CDE session but each time i try to start it System Managment Homepage starts , so i telneted to server from a pc to start sam in TUI mode is there any other way to set my SAM to... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

6. UNIX for Advanced & Expert Users

where do the configuration files from Redhat (fedora) authconfig-tui reside?

I have tried moving out the /etc/ldap.conf as well as /etc/openldap/ldap.conf files. I have LDAP Authentication turned on in the TUI. It lets me define a host and base, but the entries are not saved to the above files. /etc/sysconfig/authconfig has a bunch of environmental variables, but none... (2 Replies)
Discussion started by: druidmatrix
2 Replies

7. Shell Programming and Scripting

[SH] TUI not always properly aligned

Heyas I havent found a thread to introduce, so i combine it with the issue i have. EDIT /* Removed Problem because solved */ My first contact with Linux was back in 1995 with slackware, beeing a gamer back then, i (sadly) didnt bother to dig deeper. I finaly joined the Linux community in... (0 Replies)
Discussion started by: sea
0 Replies

8. What is on Your Mind?

TUI for Raspery Pi?

Heyas Just followed a conversation on IRC#ffmpeg, actualy just from the logs as they were offline when i came back. Anyway, they were talking about a terminal interface for their Raspery Pi using SSH. But it might just be a great usage case for TUI. It should display well, i hope, but i... (2 Replies)
Discussion started by: sea
2 Replies

9. What is on Your Mind?

Wanted: Feedback on TUI (2)

Hello everyone It just so happend that TUI was rejected from GNU for the moment, with one of the reasons beeing that additional user feedback was required. So, if you like scripting, bash in specific, please have a try and report your feedback, to help me find all issues to fix, and as i... (0 Replies)
Discussion started by: sea
0 Replies

10. Shell Programming and Scripting

Feedback wanted for upcoming script language

Hi I'm currently rewriting a project from install-required to a pure runtime form. The former had required the project name and the definition of the command as name, as they all become functions now, this could be shorter. As you might have figured, the project already exists in another... (3 Replies)
Discussion started by: sea
3 Replies
GIMPTOOL(1)							 GIMP Manual Pages						       GIMPTOOL(1)

NAME
gimptool - perform various Gimpy functions SYNOPSIS
gimptool [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--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] [--uninstall-admin-script script.scm] DESCRIPTION
gimptool 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 can also be used by programs that need to know what libraries and include-paths Gimp was compiled with. This is especially useful in Makefiles. On Unix, gimptool is a script. On Windows, it is a program. They should be more or less compatible. This manual page describes the Unix script version. OPTIONS
gimptool 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 dont actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but dont actually execute them. Same as -n. --dry-run Test mode. Print the commands but dont actually execute them. Same as -n. --recon Test mode. Print the commands but dont actually execute them. Same as -n. --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 plugins 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-1.2/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-1.2/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin plug-in Install plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-script script.scm Install script.scm into the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --install-admin-script script.scm Install script.scm into the system-wide Gimp script directory (/usr/share/gimp/1.2/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide Gimp script directory (/usr/share/gimp/1.2/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 plugins that do not require the GTK libs. --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 plugins that do not require the GTK libs. --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
GTK_CONFIG to get the location of the gtk-config program. 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. DESTDIR to add a prefix to the install/uninstall path. LDFLAGS to get the prefered flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . GTK_CONFIG path to the gtk-config shell script used by gimptool and in the build process of many gtk apps. SEE ALSO
gimp(1), gimprc(5), gimp-remote(1), gtk-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and 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>). COPYRIGHT
Copyright (C) 1998 Owen Taylor and Manish Singh Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in sup- porting documentation. Version 1.2.3 26 June 2001 GIMPTOOL(1)
All times are GMT -4. The time now is 01:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy