Sponsored Content
Full Discussion: One liners, quick rant...
The Lounge What is on Your Mind? One liners, quick rant... Post 302977438 by jim mcnamara on Monday 18th of July 2016 07:17:52 AM
Old 07-18-2016
Scrutinizer - sysadmins do put two or three commands together on the fly. I do. Pipe this command into this other command and then sort the output. That is essentially what the -exec predicate does for the find command.

Scripts coded as giant one-liners are out of bounds. Period. rbatte1 covers why really well.

I thought we were discussing the massive one-liners we see here a lot. We seem to want to define good and bad one-liners here. So let's say one-liners in scripts meant to be part of production should not be written as "multi-blobs" of piped commands.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Where can I rant?

First of all, apologies to the admins for not reading the rules totally and missing the bit about ranting off about other OSs. But that raises a question. Where do you go to have a good rant, to vent your disgust at various corporations and thier hideous behaviour? :confused: (2 Replies)
Discussion started by: u6ik
2 Replies

2. Shell Programming and Scripting

awk - one liners

Guys, I have a requirement like this. A file has >5K records always. Separated by "|", it has 30 fields for each line. In some lines, I am getting an odd field. say, the 15th field is supposed to be 2 characters but comes in as >2. In this case, for resolving this I need to copy the value of... (6 Replies)
Discussion started by: PikK45
6 Replies

3. What is on Your Mind?

Those simple one liners

I wanted to say LOL and punch my face when I saw post#11 (where Don_Cragun even reduced the string manipulation with a simple regex) in the thread https://www.unix.com/shell-programming-scripting/220553-add-0-start-filename-2.html I mean, when things can be done with just a one liner, sometimes I... (6 Replies)
Discussion started by: ahamed101
6 Replies

4. What is on Your Mind?

A rant...

Hi guys... (Apologies for any typos etc...) This is basically a rant. I have been doing kids level projects and writing code to suit since around 1982, for the uProfessor, for the Sinclair Spectrum and later for the QL, IBM-XT in MS-DOS and after that for a 386DX40 up to Windows 95, until I... (3 Replies)
Discussion started by: wisecracker
3 Replies
DH-EXEC(1)							      dh-exec								DH-EXEC(1)

NAME
dh-exec - Debhelper executable file helpers SYNOPSIS
#! /usr/bin/dh-exec src/libfoo-*.so.* debian/foo-plugins/usr/lib/foo/${DEB_HOST_MULTIARCH}/ etc/example.conf => debian/foo/etc/foo/foo.conf DESCRIPTION
dh-exec is a simple program, meant to be used as the interpreter for executable debhelper config files. It is a wrapper around the various other sub-commands (see below), and will pipe the input file through all of them in turn, using an ordering that makes most sense in the vast majority of cases. The order as of now is dh-exec-subst gets run first, followed by dh-exec-install, so that variable expansion happens before files need to be copied. ARCHITECTURE
dh-exec is built up from three layers: there is the dh-exec utility, its single entry point, the only thing one will need to call. Below that, there are the various sub-commands, such as dh-exec-subst, dh-exec-installs and dh-exec-illiterate, which are thin wrappers around the various dh-exec scripts, that make sure they only run those that need to be run. And the lowest layer are the various scripts that do the actual work. One can control which sub-commands to run, or if even more granularity is desired, one can limit which scripts shall be run, too. See below for the options! OPTIONS
--with=command[,command ...] Replace the list of sub-commands to run the input through with a custom list (where entries are separated by whitespace or commas). This option will always replace the existing list with whatever is specified. This can be used to explicitly set which sub-commands to use. The list must not include the dh-exec- prefix. Defaults to subst,install. --without=command[,command ...] Inversely to the option above, this lists all the sub-commands which should not be used. The list must not include the dh-exec- prefix. --with-scripts=script[,script ...] Replace the list of scripts to run the input through with a custom list (where entries are separated by whitespace or commas). This option will always replace the existing list with whatever is specified. This can be used to explicitly specify which scripts to use, limiting even beyond what the --with option is capable of. The list must not include the dh-exec- prefix. By default it is empty, meaning there is no filtering done, and whatever scripts the sub-commands find, will be run. --no-act Do not really do anything, but print the pipeline that would have been run instead. --list List the available sub-commands and scripts, grouped by sub-command. --help, --version Display a short help or the package version, respectively. SUB-COMMANDS dh-exec-subst Substitutes various variables (either from the environment, or from dpkg-architecture(1)). dh-exec-install An extension to dh_install(1), that supports renaming files during the copy process, using a special syntax. ENVIRONMENT
DH_EXEC_LIBDIR The directory in which the wrapped sub-commands reside. Defaults to /usr/lib/dh-exec/. DH_EXEC_SCRIPTDIR The directory in which the scripts that do the heavy work live. Defaults to /usr/share/dh-exec/. FILES
$DH_EXEC_LIBDIR/dh-exec-* The various sub-commands. $DH_EXEC_SCRIPTDIR/dh-exec-* The various scripts ran by the sub-commands. SEE ALSO
debhelper(1), dh-exec-subst(1), dh-exec-install(1) AUTHOR
dh-exec is copyright (C) 2011-2012 by Gergely Nagy <algernon@madhouse-project.org>. 2012-05-03 DH-EXEC(1)
All times are GMT -4. The time now is 08:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy