[repo.or.cz] nomnom.git branch next updated: v0.2.0-20-gb870a82
Brought to you by:
legatvs
|
From: <nom...@li...> - 2011-10-30 09:56:21
|
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project nomnom.git.
The branch, next has been updated
via b870a8205a75aab21aed05409f439c37e82d8b0c (commit)
from de755375c57f4be78c827cc581cb9ea7a8a58b95 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://repo.or.cz/w/nomnom.git/commit/b870a8205a75aab21aed05409f439c37e82d8b0c
commit b870a8205a75aab21aed05409f439c37e82d8b0c
Author: Toni Gundogdu <le...@gm...>
Date: Sun Oct 30 11:40:08 2011 +0200
Revise README.packagers
diff --git a/README.packagers b/README.packagers
index 59be41d..b01d26e 100644
--- a/README.packagers
+++ b/README.packagers
@@ -5,43 +5,39 @@ PACKAGERS
Prerequisites
-------------
-Make sure you read the INSTALL file for the application prerequisites.
+See the INSTALL file.
-System wide configuration file
+System-wide configuration file
------------------------------
-You can distribute 0.2 without a system wide configuration file.
+If you choose to install NomNom with a system-wide configuration file,
+please keep in mind that the users may override the values in the settings
+at any time.
-NomNom was, until 0.2, a tedious application to configure -- which is
-why installing a system wide config file with predefined values was
-previously a recommended step.
-
-You may still do this, if you like. Refer to the Qt documentation
-(look up QSettings) for the typical search paths, e.g. on Unix-like
-systems:
+Refer to the Qt documentation (look up QSettings) for the typical search
+paths as they tend to vary on how Qt was configured. For example, on a
+typical Unix-like systems these may be:
/etc/xdg/NomNom/NomNom.conf
/etc/xdg/NomNom.conf
/etc/NomNom.conf
-Keep in mind, however, that the "system wide config values" are nothing
-more than recommendations as the users may override them (in settings) at
-anytime.
-
-Example (/etc/NomNom.conf):
+Example: Force the application to use command "/foo/bar" instead of
+ default "quvi"
[Settings]
- ParseUsing=other:
+ ParseUsing=other^
ParseUsingOther=/foo/bar^-f -b %u
-Make a note of the use of "other". This would make "/foo/bar" to be
-used as the default value for "Parse using" command. The command line
-arguments follow after the "^".
-
-Full list of the supported variables, can be found in:
+You can tell the application to use a custom command by setting (in
+this case) "ParseUsing" to "other^" and then add the "ParseUsingOther"
+variable that defines the (path) to the custom command with the args.
+Make also a note of the "^" that separates the command and the args.
+For other supported Settings variables, see:
$top_srcdir/src/settings/nsettings.cpp
-Or take a look at your local user config. Run "nomnom --config-path"
-to find the path to it.
+Or, alternatively, you could use your own local config file as a
+template config file. To find the path to the file, run:
+ nomnom --config-path
-----------------------------------------------------------------------
Summary of changes:
README.packagers | 42 +++++++++++++++++++-----------------------
1 files changed, 19 insertions(+), 23 deletions(-)
repo.or.cz automatic notification. Contact project admin le...@gm...
if you want to unsubscribe, or site admin ad...@re... if you receive
no reply.
--
nomnom.git ("The graphical media download tool")
|