savannah-register-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #11768] Submission of uqjau: framework


From: Tom Rodman
Subject: [Savannah-register-public] [task #11768] Submission of uqjau: framework of mostly bash and some perl: scripts, script functions, and script m4 macros for a range of simple purposes, divided into "packages" (directories) by category.
Date: Sat, 28 Jan 2012 21:19:42 +0000
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1

URL:
  <http://savannah.gnu.org/task/?11768>

                 Summary: Submission of uqjau: framework of mostly bash and
some perl: scripts, script functions, and script m4 macros for a range of
simple purposes, divided into "packages" (directories) by category.
                 Project: Savannah Administration
            Submitted by: sldzsrq
            Submitted on: Sat 28 Jan 2012 09:19:41 PM GMT
         Should Start On: Sat 28 Jan 2012 12:00:00 AM GMT
   Should be Finished on: Tue 07 Feb 2012 12:00:00 AM GMT
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

A new project has been registered at Savannah 
This project account will remain inactive until a site admin approves or
discards the registration.


= Registration Administration =

While this item will be useful to track the registration process, *approving
or discarding the registration must be done using the specific Group
Administration
<https://savannah.gnu.org/siteadmin/groupedit.php?group_id=10937> page*,
accessible only to site administrators, effectively *logged as site
administrators* (superuser):

* Group Administration
<https://savannah.gnu.org/siteadmin/groupedit.php?group_id=10937>


= Registration Details =

* Name: *uqjau: framework of mostly bash and some perl: scripts, script
functions, and script m4 macros for a range of simple purposes, divided into
"packages" (directories) by category.*
* System Name:  *uqjau*
* Type: non-GNU software & documentation
* License: GNU General Public License v2 or later

----

==== Description: ====
uqjau: framework of mostly bash and some perl: scripts, script
functions, and script m4 macros for a range of simple purposes,
divided into "packages" (directories) by category.

- Directory layout and tool configuration was influenced by
  'slashpackage': http://cr.yp.to/slashpackage.html. There is a
  directory w/basename 'commands' that you may place in your
  PATH; it contains only symbolic links to scripts.

- No requirement for record on file system or in env vars of
  where install tree is. Scripts figure this out. Does not
  depend on a fixed name for top dir in install tree.

- The goal was to write the scripts so that the 'commands'
  dir does not have to be in the PATH - scripts that are the
  exception, are not located in the
  uqjau tree, but depend on files in it.

- After a script determines path to root of the uqjau
  install dir, it may source supporting (dependency) files in
  the uqjau tree.

- Scripts should not depend on pre-existing env vars, so cron
  jobs that run scripts should work w/o wrapper scripts.

- Scripts may only be invoked by: their basename ( assuming
  the 'commands' dir is in the PATH ); by the fully qualified
  pathname to the 'commands' or 'scommands' dir; or by
  ./COMMANDBASENAME - only if current working dir is the
  'commands' dir.  This limitation in the last case is due to
  the logic used in most scripts that try to determine the
  install dir for uqjau.



==== Other Comments: ====
Attempted to enforce my own notion of scripting best practices.
I have over 20 years of work or hobby experience writing and
maintaining shell scripts.

I lean towards sys admin work, and spend hours each day at the
bash commandline - these scripts support day to day work.



==== Tarball URL: ====
http://trodman.com/uqjau/






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?11768>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]