- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -15,7 +15,14 @@
     # edit "${sysconfdir}"/rpstir/rpstir.conf as desired
     rpstir-initialize -f
 
-This ticket is about simplifying the installation procedure by doing the 
equivalent during `make install` (probably via the `install` utility), except 
for the last two lines:
+This ticket is about simplifying the installation procedure by doing something 
similar during `make install` (probably via the `install` utility).
 
-  * the user will need to edit `rpstir.conf`, but we can at least have 
sensible defaults that just work for 99% of users
-  * running `rpstir-initialize -f` is bad if the user is upgrading
+* `etc/rpstir.conf.in` should be modified to use sensible defaults for all 
parameters except for `DatabasePassword`. `DatabasePassword` should be set by 
`make install`.
+* `configure.ac` should be modified to:
+    * take optional `--with-user=` and `--with-group=` parameters
+    * test for (but don't require) the presence of a pseudo-random number 
generating file (e.g., `/dev/urandom`) 
+* `make install` should be modified to:
+    * When installing `"${docdir}"/examples/rpstir.conf`, set 
`DatabasePassword` to an example password.
+    * Create the directories mentioned above and in the `README`. If the 
username and/or group were specified to `configure`, use those. Otherwise, use 
the current user/group.
+    * If `"${sysconfdir}"/rpstir/rpstir.conf` does not exist, and a PRNG 
device is available, install `etc/rpstir.conf.in` to 
`"${sysconfdir}"/rpstir/rpstir.conf` and set `DatabasePassword` to a random 
password. (TODO: there should be another ticket about modifying everything that 
uses the database to attempt to initialize the database as needed.)
+* `README` should be updated

~~~~




---

** [tickets:#16] do post-installation proecudres as part of 'make install'**

**Status:** unread
**Created:** Sun Jun 07, 2015 07:59 PM UTC by Richard Hansen
**Last Updated:** Sun Jun 07, 2015 07:59 PM UTC
**Owner:** nobody

The `README` currently has a section dedicated to post-installation procedures 
that boils down to this:

    for d in \
        "${sysconfdir}"/rpstir \
        "${localstatedir}"/cache/rpstir \
        "${localstatedir}"/log/rpstir \
        "${localstatedir}"/lib/rpstir \
        ;
    do
        mkdir -p "${d}"
        chmod -R o-rwx "${d}"
    done
    [ -f "${sysconfdir}"/rpstir/rpstir.conf ] \
        || cp "${docdir}"/examples/rpstir.conf "${sysconfdir}"/rpstir
    # edit "${sysconfdir}"/rpstir/rpstir.conf as desired
    rpstir-initialize -f

This ticket is about simplifying the installation procedure by doing something 
similar during `make install` (probably via the `install` utility).

* `etc/rpstir.conf.in` should be modified to use sensible defaults for all 
parameters except for `DatabasePassword`. `DatabasePassword` should be set by 
`make install`.
* `configure.ac` should be modified to:
    * take optional `--with-user=` and `--with-group=` parameters
    * test for (but don't require) the presence of a pseudo-random number 
generating file (e.g., `/dev/urandom`) 
* `make install` should be modified to:
    * When installing `"${docdir}"/examples/rpstir.conf`, set 
`DatabasePassword` to an example password.
    * Create the directories mentioned above and in the `README`. If the 
username and/or group were specified to `configure`, use those. Otherwise, use 
the current user/group.
    * If `"${sysconfdir}"/rpstir/rpstir.conf` does not exist, and a PRNG device 
is available, install `etc/rpstir.conf.in` to 
`"${sysconfdir}"/rpstir/rpstir.conf` and set `DatabasePassword` to a random 
password. (TODO: there should be another ticket about modifying everything that 
uses the database to attempt to initialize the database as needed.)
* `README` should be updated


---

Sent from sourceforge.net because rpstir-devel@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/rpstir/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/rpstir/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
rpstir-devel mailing list
rpstir-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpstir-devel

Reply via email to