LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-04-2014, 11:29 PM   #1
Xsane
Member
 
Registered: Jan 2014
Posts: 31

Rep: Reputation: 3
Slackware Package Tools Terse Patch


I sent these patches to Pat and Roberto 2 months ago,
but received no response. So I'll post them here to
see if any of the Slackware community find the
changes as useful as I do.

I started this patch because when keeping my
systems up to date with slackpkg upgrade-all there
was so much noise in the output that made it
difficult to easily see what packages had been
updated properly.

Installpkg already has a 'terse' option to reduce
its verbosity. These patches add the 'terse'
option to removepkg and upgradepkg. So now this
option is consistent across the package tools.

Also, in the name of consistency, installpkg and
removepkg accept both -OPTION and --OPTION, but
upgradepkg did not. Now they will all accept either
single or double dash options(so we don't have to
remember which is which anymore).

Finally, I added an ENV VAR named TERSEPKG that
all Slackware package tools honor. Now when running
other utilities that call Slackware package tools,
as slackpkg does, terse mode can be used even if
those other utilities do not support it directly.

I then added these same features to slackpkg
itself.

Here are examples of different ways the changes
can be used:


TERSEPKG=1 slackpkg upgrade-all
OR
slackpkg -terse=on upgrade-all


TERSEPKG=1 [installpkg | removepkg | upgradepkg ]
OR
installpkg [-terse | --terse]
removepkg [-terse | --terse]
upgradepkg [-terse | --terse]



The Patches:

Code:
--- installpkg.orig	2011-04-22 16:50:43.000000000 -0400
+++ installpkg	2014-04-02 11:56:49.702802107 -0400
@@ -21,6 +21,9 @@
 #  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 #
+# Mon Mar 31 19:14:15 EDT 2014 Xsane
+# Added TERSEPKG ENV
+#
 # Fri Apr 22 20:45:45 UTC 2011
 # A stronger formula is needed to regularize output that will be parsed.
 unset LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY \
@@ -187,7 +190,11 @@
 }
 
 # Parse options:
+if [ $TERSEPKG ]; then
+MODE=terse
+else
 MODE=install # standard text-mode
+fi
 while [ 0 ]; do
   if [ "$1" = "-warn" -o "$1" = "--warn" ]; then
     MODE=warn
Code:
--- removepkg.orig	2009-04-28 16:44:26.000000000 -0400
+++ removepkg	2014-04-02 18:17:22.918159700 -0400
@@ -1,6 +1,9 @@
 #!/bin/sh
 # Slackware remove package script
 #
+# Revision 12.34567890c Mon Mar 31 19:17:45 EDT 2014 Xsane
+# Added -terse option and TERSEPKG ENV.
+#
 # Sat Apr 25 21:18:53 UTC 2009 (12.34567890b)
 # Converted to use new pkgbase() function to remove pathname and
 # valid package extensions.
@@ -177,11 +180,11 @@
  while read FILE ; do
   if [ ! -d "$ROOT/$FILE" ]; then
    if [ -r "$ROOT/$FILE" ]; then
-    echo "  --> $ROOT/$FILE was found in another package. Skipping."
+    $ECHO "  --> $ROOT/$FILE was found in another package. Skipping."
     preserve_file "$FILE"
    else
     if [ "$(echo $FILE | cut -b1-8)" != "install/" ]; then
-     echo "WARNING: Nonexistent $ROOT/$FILE was found in another package. Skipping."
+     $ECHO "WARNING: Nonexistent $ROOT/$FILE was found in another package. Skipping."
     fi
    fi
   else
@@ -193,9 +196,9 @@
 keep_links() {
  while read LINK ; do
   if [ -L "$ROOT/$LINK" ]; then
-   echo "  --> $ROOT/$LINK (symlink) was found in another package. Skipping."
+   $ECHO "  --> $ROOT/$LINK (symlink) was found in another package. Skipping."
   else
-   echo "WARNING: Nonexistent $ROOT/$LINK (symlink) was found in another package. Skipping."
+   $ECHO "WARNING: Nonexistent $ROOT/$LINK (symlink) was found in another package. Skipping."
   fi
  done
 }
@@ -208,14 +211,14 @@
      echo "WARNING: $ROOT/$FILE changed after package installation."
     fi
     if [ ! "$WARN" = "true" ]; then
-     echo "  --> Deleting $ROOT/$FILE"
+     $ECHO "  --> Deleting $ROOT/$FILE"
      preserve_file "$FILE" && rm -f "$ROOT/$FILE"
     else
      echo "  --> $ROOT/$FILE would be deleted"
      preserve_file "$FILE"
     fi
    else
-    echo "  --> $ROOT/$FILE no longer exists. Skipping."
+    $ECHO "  --> $ROOT/$FILE no longer exists. Skipping."
    fi
   else
    preserve_dir "$FILE"
@@ -227,13 +230,13 @@
  while read LINK ; do
   if [ -L "$ROOT/$LINK" ]; then
    if [ ! "$WARN" = "true" ]; then
-    echo "  --> Deleting symlink $ROOT/$LINK"
+    $ECHO "  --> Deleting symlink $ROOT/$LINK"
     rm -f $ROOT/$LINK
    else
     echo "  --> $ROOT/$LINK (symlink) would be deleted"
    fi
   else
-   echo "  --> $ROOT/$LINK (symlink) no longer exists. Skipping."
+   $ECHO "  --> $ROOT/$LINK (symlink) no longer exists. Skipping."
   fi
  done
 }
@@ -244,7 +247,7 @@
   if [ -d "$ROOT/$DIR" ]; then
     if [ ! "$WARN" = "true" ]; then
       if [ $(ls -a "$ROOT/$DIR" | wc -l) -eq 2 ]; then
-        echo "  --> Deleting empty directory $ROOT/$DIR"
+        $ECHO "  --> Deleting empty directory $ROOT/$DIR"
         rmdir "$ROOT/$DIR"
       else
         echo "WARNING: Unique directory $ROOT/$DIR contains new files"
@@ -261,7 +264,7 @@
  while read FILE ; do
    if [ -f "$ROOT/$FILE" ]; then
      if [ ! "$WARN" = "true" ]; then
-       echo "  --> Deleting $ROOT/$FILE (fmt man page)"
+       $ECHO "  --> Deleting $ROOT/$FILE (fmt man page)"
        rm -f $ROOT/$FILE
      else
        echo "  --> $ROOT/$FILE (fmt man page) would be deleted"
@@ -311,7 +314,7 @@
  for PKGLIST in $* 
  do
   PKGNAME=$(pkgbase $PKGLIST)
-  echo
+  $ECHO
   # If we don't have a package match here, then we will attempt to find
   # a package using the long name format (name-version-arch-build) for
   # which the base package name was given.  On a properly-managed machine,
@@ -345,7 +348,7 @@
     TRIGGER="FILE LIST:"
    fi
    if [ ! "$WARN" = true ]; then
-    echo "Removing files:"
+    $ECHO "Removing files:"
    fi
    sed -n "/$TRIGGER/,/^$/p" < $ADM_DIR/packages/$PKGNAME | \
     fgrep -v "FILE LIST:" | sort -u > $TMP/delete_list$$
@@ -398,16 +401,23 @@
 }
 
 if [ "$#" = "0" ]; then
-  echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1
+  echo "Usage: $(basename $0) [-terse] [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1
+fi
+
+if [ $TERSEPKG ]; then
+ECHO="true"
+else
+ECHO="echo"
 fi
 
 while : ; do
  case "$1" in
+  -terse | --terse) ECHO=true; shift;;
   -copy | --copy) WARN=true; PRESERVE=true; shift;;
   -keep | --keep) KEEP=true; shift;;
   -preserve | --preserve) PRESERVE=true; shift;;
   -warn | --warn) WARN=true; shift;;
-  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1;;
+  -* | --*) echo "Usage: $(basename $0) [-terse] [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1;;
   *) break
  esac
 done
Code:
--- upgradepkg.orig	2010-05-11 12:41:49.000000000 -0400
+++ upgradepkg	2014-04-02 18:17:33.612161124 -0400
@@ -34,6 +34,12 @@
 # Support new compression types and package extensions.
 # Converted to use new pkgbase() function to remove pathname and
 # valid package extensions.
+#
+# Sun Mar 30 23:51:10 EDT 2014 Xsane
+# Added --terse and ENV TERSEPKG
+# Added -OPTION for consistency with installpkg and removepkg
+# Added options(sans no-paranoia) to help output.
+#
 
 # Return a package name that has been stripped of the dirname portion
 # and any of the valid extensions (only):
@@ -62,8 +68,8 @@
 usage() {
  cat << EOF
 
-Usage: upgradepkg newpackage [newpackage2 ... ]
-       upgradepkg oldpackage%newpackage [oldpackage2%newpackage2 ... ]
+Usage: upgradepkg [options] newpackage [newpackage2 ... ]
+       upgradepkg [options] oldpackage%newpackage [oldpackage2%newpackage2 ... ]
 
 Upgradepkg upgrades a Slackware package (.tgz, .tbz, .tlz, .txz) from an
 older version to a newer one.  It does this by INSTALLING the new package
@@ -83,6 +89,15 @@
 
    ROOT=/mnt upgradepkg package.tgz (or .tbz, .tlz, .txz)
 
+Options:      
+  --help         Show this page.
+  --install-new  Install packages even when no matches are found.
+  --reinstall    Reinstall packages even when installed version matches.
+  --verbose, -v  Increase verbosity.
+  --terse        Decrease verbosity.
+  --dry-run      Report which packages would be installed or upgraded
+                 but don't actually perform the upgrades.
+               
 EOF
 }
 
@@ -104,14 +119,22 @@
 fi
 
 # --help or no args?
-if [ "$1" = "" -o "$1" = "--help" -o "$1" = "-?" ]; then
+if [ "$1" = "" -o "$1" = "--help" -o "$1" = "-help" -o "$1" = "-?" ]; then
   usage;
   exit 1;
 fi
 
+if [ $TERSEPKG ]; then
+MODE="-terse "
+ECHO="true"
+else
+MODE=""
+ECHO="echo"
+fi
+
 # Arg processing loop.  These must come before any packages are listed.
 while [ 0 ]; do
-  if [ "$1" = "--no-paranoia" ]; then
+  if [ "$1" = "--no-paranoia" -o "$1" = "-no-paranoia" ]; then
     # Enable --no-paranoia mode.  This is so not-recommended that we're
     # not even going to document it. ;)   If a file used to be directly
     # managed and now is moved into place, using --no-paranoia will cause
@@ -119,20 +142,25 @@
     # Don't use it.
     NOT_PARANOID="true"
     shift 1
-  elif [ "$1" = "--install-new" ]; then
+  elif [ "$1" = "--terse" -o "$1" = "-terse" ]; then
+    # Ask removepkg and installpkg to be quiet, please.
+    MODE="-terse "
+    ECHO="true"
+    shift 1
+  elif [ "$1" = "--install-new" -o "$1" = "-install-new" ]; then
     # Install packages that do not already have an installed version.
     # The usual default is to skip them.
     INSTALL_NEW="yes"
     shift 1
-  elif [ "$1" = "--reinstall" ]; then
+  elif [ "$1" = "--reinstall" -o "$1" = "-reinstall" ]; then
     # Reinstall packages even if the installed one is the same version.
     REINSTALL="true"
     shift 1
-  elif [ "$1" = "--verbose" -o "$1" = "-v" ]; then
+  elif [ "$1" = "--verbose" -o "$1" = "-verbose" -o "$1" = "-v" ]; then
     # We're adding a --verbose mode that doesn't filter removepkg as much
     VERBOSE="verbose"
     shift 1
-  elif [ "$1" = "--dry-run" ]; then
+  elif [ "$1" = "--dry-run" -o "$1" = "-dry-run" ]; then
     # Output a report about which packages would be installed or upgraded
     # but don't actually perform the upgrades.
     DRY_RUN="true"
@@ -245,7 +273,7 @@
 +==============================================================================
 
 EOF
-      /sbin/installpkg $INCOMINGDIR/$NNAME
+      /sbin/installpkg ${MODE}$INCOMINGDIR/$NNAME
     fi
   fi
   shift 1
@@ -326,7 +354,7 @@
   /sbin/installpkg $INCOMINGDIR/$NNAME
   RETCODE=$?
 else
-  echo "Pre-installing package $NEW..."
+  $ECHO "Pre-installing package $NEW..."
   /sbin/installpkg $INCOMINGDIR/$NNAME 1> /dev/null
   RETCODE=$?
 fi
@@ -349,7 +377,7 @@
       if [ "$VERBOSE" = "verbose" ]; then
         ROOT=$ROOT /sbin/removepkg $rempkg
       else
-        ROOT=$ROOT /sbin/removepkg $rempkg | grep -v "Skipping\." | grep -v "Removing files:"
+        ROOT=$ROOT /sbin/removepkg ${MODE}$rempkg | grep -v "Skipping\." | grep -v "Removing files:"
       fi
     done
   )
@@ -359,21 +387,21 @@
       if [ "$VERBOSE" = "verbose" ]; then
         /sbin/removepkg $rempkg
       else
-        /sbin/removepkg $rempkg | grep -v "Skipping\." | grep -v "Removing files:"
+        /sbin/removepkg ${MODE}$rempkg | grep -v "Skipping\." | grep -v "Removing files:"
       fi
     done
   )
 fi
-echo
+$ECHO
 
 # Again!  Again!
 # Seriously, the reinstalling of a package can be crucial if any files
 # shift location, so we should always reinstall as the final step:
 if [ ! "$NOT_PARANOID" = "true" ]; then
-  /sbin/installpkg $INCOMINGDIR/$NNAME
+  /sbin/installpkg ${MODE}$INCOMINGDIR/$NNAME
 fi
 
-echo "Package $OLD upgraded with new package $INCOMINGDIR/$NNAME."
+$ECHO "Package $OLD upgraded with new package $INCOMINGDIR/$NNAME."
 ERRCODE=0
 
 # Process next parameter:
Code:
--- slackpkg.orig	2011-03-24 22:42:10.000000000 -0400
+++ slackpkg	2014-04-02 11:57:32.339768320 -0400
@@ -40,6 +40,14 @@
 . $CONF/slackpkg.conf
 ERROR=""
 
+# Honor TERSEPKG ENV
+if [ $TERSEPKG ]; then
+ECHO="true"
+else
+ECHO="echo"
+fi
+MODE=''
+
 # Set temporary directory
 #
 TMPDIR=$(mktemp -p /tmp -d slackpkg.XXXXXX 2>/dev/null)
@@ -63,6 +71,11 @@
 
 while [ -n "$1" ] ; do
   case $1 in
+    -terse=on)
+      MODE='--terse '
+      ECHO="true"
+      shift
+    ;;
     -delall=on)
       DELALL=on
       shift
Code:
--- core-functions.sh.orig	2013-09-17 16:36:36.000000000 -0400
+++ core-functions.sh	2014-04-02 13:12:28.244600063 -0400
@@ -861,7 +861,7 @@
 			echo -e "${NAMEPKG}:\t$ERROR" >> $TMPDIR/error.log
 		fi
 	else
-		echo -e "\tPackage $1 is already in cache - not downloading" 
+		$ECHO -e "\tPackage $1 is already in cache - not downloading" 
 	fi
 
 	# Check if we have sufficient disk space to install selected package
@@ -909,13 +909,13 @@
 				echo -e "\tInstalling ${1/%.t[blxg]z/}..."
 			;;
 			upgradepkg)
-				echo -e "\tUpgrading ${1/%.t[blxg]z/}..."
+				$ECHO -e "\tUpgrading ${1/%.t[blxg]z/}..."
 			;;
 			*)
 				echo -e "\c"
 			;;
 		esac	
-		( cd $CACHEPATH && $2 $1 )
+		( cd $CACHEPATH && $2 ${MODE}$1 )
 	else 
 		rm $CACHEPATH/$1 2>/dev/null
 		echo -e "\tERROR - Package not installed! $ERROR error!"
 
Old 06-05-2014, 04:22 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,334

Rep: Reputation: Disabled
I think having an option to use the "--terse" parameter to installpkg is nice, however you are confusing "terse" with "non-verbose". I don't see why all slackpkg's echo statements should be masked out if you want terse output from installpkg.

Eric
 
Old 06-05-2014, 08:36 AM   #3
Xsane
Member
 
Registered: Jan 2014
Posts: 31

Original Poster
Rep: Reputation: 3
Quote:
Originally Posted by Alien Bob View Post
you are confusing "terse" with "non-verbose".
Terse and non-verbose are synonyms. I agree that a verbose option would have been a better choice for installpkg. I did not make that choice. I only conform to the long established use of --terse in installpkg. Changing the option name now would break things.

Quote:
Originally Posted by Alien Bob View Post
I don't see why all slackpkg's echo statements should be masked out if you want terse output from installpkg.
I don't want a terse output from installpkg... we already have that.

What I want is a terse output from slackpkg so that I can see what it has done without screen, after screen, after screen, of file paths being printed when slackpkg calls upgradepkg. Especailly bad with packages that contain a large number of files like anything Mozilla, or PHP, or similarly large packages.

And I did make it an option, nobody would have to use it. Choice is good, yes?

Last edited by Xsane; 06-05-2014 at 08:51 AM.
 
Old 06-05-2014, 11:04 AM   #4
Xsane
Member
 
Registered: Jan 2014
Posts: 31

Original Poster
Rep: Reputation: 3
Quote:
Originally Posted by Alien Bob View Post
I don't see why all slackpkg's echo statements should be masked out...
I don't mask all echo statements. I selectively mask them for a 'terse' output.
The greatest reduction in slackpkg's output comes from the removepkg patch.

Here is the output from a recent update on one of my boxes using:

slackpkg -terse=on upgrade-all

Code:

+==============================================================================
| Upgrading mariadb-5.5.35-x86_64-1_slack14.1 package using ./mariadb-5.5.37-x86_64-1_slack14.1.txz
+==============================================================================

Removing package /var/log/packages/mariadb-5.5.35-x86_64-1_slack14.1-upgraded-2014-06-03,17:18:48...
mariadb-5.5.37-x86_64-1_slack14.1: Drop-in replacement for the MySQL Dat [157M]


+==============================================================================
| Upgrading seamonkey-2.25-x86_64-1_slack14.1 package using ./seamonkey-2.26-x86_64-1_slack14.1.txz
+==============================================================================

Removing package /var/log/packages/seamonkey-2.25-x86_64-1_slack14.1-upgraded-2014-06-03,17:19:42...
seamonkey-2.26-x86_64-1_slack14.1: SeaMonkey an open-source web browser  [110M]


+==============================================================================
| Upgrading seamonkey-solibs-2.25-x86_64-1_slack14.1 package using ./seamonkey-solibs-2.26-x86_64-1_slack14.1.txz
+==============================================================================

Removing package /var/log/packages/seamonkey-solibs-2.25-x86_64-1_slack14.1-upgraded-2014-06-03,17:20:57...
seamonkey-solibs-2.26-x86_64-1_slack14.1: Shared libraries from Seamonke [3.8M]


Searching for NEW configuration files
                No .new files found.
Of course, all the wget stuff happens before the output shown above(providing the default configuration to download all before upgrading is used).

I find this concise list of what was upgraded very useful. Maybe I'm alone in this opinion?
 
Old 06-06-2014, 04:25 AM   #5
Slax-Dude
Member
 
Registered: Mar 2006
Location: Valadares, Portugal
Distribution: Slackware
Posts: 267

Rep: Reputation: 72
Quote:
Originally Posted by Xsane View Post
I find this concise list of what was upgraded very useful. Maybe I'm alone in this opinion?
No you are not
Thank you very much for these patches. I'll test them tonight on my test system.
 
Old 06-06-2014, 04:36 AM   #6
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,081
Blog Entries: 52

Rep: Reputation: Disabled
Looks like a useful option to me, too.
 
Old 06-06-2014, 05:49 AM   #7
55020
Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 418
Blog Entries: 4

Rep: Reputation: 426Reputation: 426Reputation: 426Reputation: 426Reputation: 426
I agree that terse was a valuable innovation and it would be great to teach upgradepkg how to do terse. Thanks for what you've already done.

Don't expect to see this in Slackware immediately - from observation, it seems that adding features to pkgtools usually has a very specific place in the workflow of creating a new release of Slackware, and we're not there yet.

I think it would be beneficial to break this down into multiple independent ideas, then it would be easier to discuss the ideal form for each of them.
  1. add an upgradepkg --terse option so that it is consistent with installpkg
  2. add a removepkg --terse option
  3. add a slackpkg option to make it invoke installpkg, upgradepkg and removepkg with --terse
  4. add a slackpkg option to make slackpkg's own messages quieter

For example, Eric was saying that 3 and 4 should be independent. Also I'm not yet convinced that there is a need for the TERSEPKG environment variable. Then you can polish the patches -- that would include the manpages too...
 
Old 06-06-2014, 09:41 AM   #8
Xsane
Member
 
Registered: Jan 2014
Posts: 31

Original Poster
Rep: Reputation: 3
Eric, Slax-Dude, brianL, 55020, thank you all for the feedback.

Slax-Dude, thank you for testing the patches.


Quote:
Originally Posted by 55020 View Post
Don't expect to see this in Slackware immediately - from observation, it seems that adding features to pkgtools usually has a very specific place in the workflow of creating a new release of Slackware, and we're not there yet.
Thank you for the insight. I asked on ##slackware how to go about this, it was suggested to just post it here. I have read more than once on this forum that it is unclear how often Pat visits here and that patches should be sent directly to him. Perhaps the correct answer is to do both?

Quote:
Originally Posted by 55020 View Post
I think it would be beneficial to break this down into multiple independent ideas, then it would be easier to discuss the ideal form for each of them.
  1. add an upgradepkg --terse option so that it is consistent with installpkg
  2. add a removepkg --terse option
  3. add a slackpkg option to make it invoke installpkg, upgradepkg and removepkg with --terse
  4. add a slackpkg option to make slackpkg's own messages quieter
Good advice. I considered offering only small changes one at a time, but they are all so interrelated, and all required to achieve the end result for slackpkg, I decided to try this much in one go. I have more ideas for improvements, but I thought, the larger I make the patch the greater the odds of rejection.

Are you suggesting that each patch should have its own thread? It seems like that would make the discussion disjointed?

If your list includes the order of discussion, removepkg should be first as the upgradpkg patch depends on the removepkg patch.

Quote:
Originally Posted by 55020 View Post
For example, Eric was saying that 3 and 4 should be independent.
Again, thank you for the insight. Perhaps Eric was being 'terse' and I wasn't smart enough to figure out what he meant.

I cannot imagine a scenario where I would call slackpkg wanting Slackware pkg tools to be terse, but slackpkg to be verbose? Having said that, I can certainly make the 3,4 patch separation you request. What would distinguish the two slackpkg options. -terse=on would only pass Slackware pkg tools --terse? What would I call the slackpkg terse mode option? I think making this distinction would be unnecessarily confusing to the end users and I'm still unclear as to its use purpose?


Quote:
Originally Posted by 55020 View Post
Also I'm not yet convinced that there is a need for the TERSEPKG environment variable.
I expected to get the most push back on this part. My reasoning is, there are already multiple utilities that call Slackware pkg tools and there may be many more in the future. It would be useful to have a way to invoke --terse mode for Slackware pkg tools even if the utility does not provide the option itself.

For example, if Pat and the team accept the Slackware pkg tools patches, but for some reason slackpkg rejects its patch. Then the users could still achieve a somewhat more concise output for slackpkg anyway. This scenario could be repeated with new utilities in the future.

End users may have no use for verbose output at all and want Slackware pkg tools to always be terse. They could add the ENV to their shell profile.

Quote:
Originally Posted by 55020 View Post
Then you can polish the patches -- that would include the manpages too...
Very true, I wanted to include man page updates. I made some changes to the usage/help output of the scripts(more could be done). The reason I stopped short of that, as stated above, is I had the notion that the longer the patches the greater the odds of rejection. I am happy to add as much as will be accepted by Pat and the team.

Last edited by Xsane; 06-06-2014 at 09:57 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Terse ? Fixit7 Puppy 6 05-12-2014 03:32 AM
A lot of (Alternative Package Tools) in Slackware .. which one is better ? alMubarmij Slackware 17 02-14-2009 08:39 AM
Many many (Package Tools) for Slackware but less (Packages) ! alMubarmij Slackware 8 02-10-2009 12:43 PM
VMware Tools Slackware package jelaiwang Slackware 1 05-27-2008 02:40 PM
Anyone know of a dvb-tools package for slackware 10.2 current? slothpuck Slackware 1 07-01-2006 11:36 AM


All times are GMT -5. The time now is 03:38 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration