msgid ""

msgstr ""

"Project-Id-Version: understanding_modules.asciidoc 0.6\n"

"POT-Creation-Date: 2013-11-07 14:18-0500\n"

"PO-Revision-Date: 2013-11-07 14:18-0500\n"

"Last-Translator: Localization SIG <centos-l10n-en@centos.org.cu>\n"

"Language-Team: English\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "Understanding Modules"

msgstr "Understanding Modules"

msgid "Oct 2013"

msgstr "Oct 2013"

msgid "Alain"

msgstr "Alain"

msgid "Reguera"

msgstr "Reguera"

msgid "Delgado"

msgstr "Delgado"

msgid "al@centos.org.cu"

msgstr "al@centos.org.cu"

msgid "ARD"

msgstr "ARD"

msgid "0.1"

msgstr "0.1"

msgid "Overview"

msgstr "Overview"

msgid ""

"From version 0.5, the <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script introduces the idea of modules to its base design. "

"Modules are a collection of functions written in Bash that can call "

"one another to create individual execution environments. They may "

"be nested to achieve high levels of maintainability and "

"extensibility. This make possible for modules writers to divide "

"complicated tasks into smaller tasks that can be easier to debug, "

"maintain and share with other modules efficiently (e.g., instead of "

"loading modules all at once, they are only loaded at demand and "

"unset once they conclude their execution)."

msgstr ""

"From version 0.5, the <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script introduces the idea of modules to its base design. "

"Modules are a collection of functions written in Bash that can call "

"one another to create individual execution environments. They may "

"be nested to achieve high levels of maintainability and "

"extensibility. This make possible for modules writers to divide "

"complicated tasks into smaller tasks that can be easier to debug, "

"maintain and share with other modules efficiently (e.g., instead of "

"loading modules all at once, they are only loaded at demand and "

"unset once they conclude their execution)."

msgid ""

"This article describes the modular design of 

"\">centos-art.sh</emphasis> script. It is a good place for you to "

"start if you are planning to contribute new module environments to "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script or want "

"to know more about how it works. The next section delves into what "

"a module environment is, the three module types you can find in it "

"and the correct way of execute each one of them."

msgstr ""

"This article describes the modular design of 

"\">centos-art.sh</emphasis> script. It is a good place for you to "

"start if you are planning to contribute new module environments to "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script or want "

"to know more about how it works. The next section delves into what "

"a module environment is, the three module types you can find in it "

"and the correct way of execute each one of them."

msgid "Module Environment"

msgstr "Module Environment"

msgid ""

"When you execute the <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script you create an execution environment in which "

"variables and functions are defined. The execution environment is "

"the higher environment inside <emphasis role=\"strong\">centos-art."

"sh</emphasis> script. It is considered to have a “global” scope, so "

"variables and functions defined in it are always available for any "

"function execution made from it. You can control the execution "

"environment of <emphasis role=\"strong\">centos-art.sh</emphasis> "

"script through files <literal>centos-art.sh</literal> and "

"<literal>centos-art.conf.sh</literal>. These files don't provide "

"too much functionality so module environments are executed from "

"<literal>centos-art.sh</literal>, to extend its functionality."

msgstr ""

"When you execute the <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script you create an execution environment in which "

"variables and functions are defined. The execution environment is "

"the higher environment inside <emphasis role=\"strong\">centos-art."

"sh</emphasis> script. It is considered to have a “global” scope, so "

"variables and functions defined in it are always available for any "

"function execution made from it. You can control the execution "

"environment of <emphasis role=\"strong\">centos-art.sh</emphasis> "

"script through files <literal>centos-art.sh</literal> and "

"<literal>centos-art.conf.sh</literal>. These files don't provide "

"too much functionality so module environments are executed from "

"<literal>centos-art.sh</literal>, to extend its functionality."

msgid ""

"Module environments are made of small functions that perform small "

"tasks and can be further executed in a specific order to produce "

"the desired result. Module environments are executed and destroyed "

"at demand. Inside <emphasis role=\"strong\">centos-art.sh</"

"emphasis>, module environments can be either “parent modules,” "

"“child modules,” or “sibling modules.”"

msgstr ""

"Module environments are made of small functions that perform small "

"tasks and can be further executed in a specific order to produce "

"the desired result. Module environments are executed and destroyed "

"at demand. Inside <emphasis role=\"strong\">centos-art.sh</"

"emphasis>, module environments can be either “parent modules,” "

"“child modules,” or “sibling modules.”"

msgid "Parent Modules"

msgstr "Parent Modules"

msgid ""

"Parent modules are initiated by executing the 

"\"strong\">tcar_setModuleEnvironment</emphasis> function with the "

"<emphasis role=\"strong\">-t parent</emphasis> option set on it. "

"Parent modules are very simple in design and you can use them to "

"implement simple solutions quickly. Normally, when you execute a "

"parent module, you initiate the highest module environment possible "

"inside <emphasis role=\"strong\">centos-art.sh</emphasis> script. "

"Because of such high scope, parent modules are frequently used to "

"define module's global variables, interpret module-specific options "

"passed through the command-line and execute the appropriate actions "

"based on them."

msgstr ""

"Parent modules are initiated by executing the 

"\"strong\">tcar_setModuleEnvironment</emphasis> function with the "

"<emphasis role=\"strong\">-t parent</emphasis> option set on it. "

"Parent modules are very simple in design and you can use them to "

"implement simple solutions quickly. Normally, when you execute a "

"parent module, you initiate the highest module environment possible "

"inside <emphasis role=\"strong\">centos-art.sh</emphasis> script. "

"Because of such high scope, parent modules are frequently used to "

"define module's global variables, interpret module-specific options "

"passed through the command-line and execute the appropriate actions "

"based on them."

msgid ""

"In <xref linkend=\"debug-parent-modules\"/>, we have executed the "

"<emphasis role=\"strong\">hello</emphasis> module with the "

"<emphasis role=\"strong\">—greeting=hi</emphasis> and 

"role=\"strong\">—debug</emphasis> options through the command-line. "

"In this example, <emphasis role=\"strong\">centos-art.sh</emphasis> "

"script executes a parent module named 

"\">hello</emphasis>, processes the module-specific options passed "

"through the command-line, prints a greeting message to standard "

"output and exits successfully."

msgstr ""

"In <xref linkend=\"debug-parent-modules\"/>, we have executed the "

"<emphasis role=\"strong\">hello</emphasis> module with the "

"<emphasis role=\"strong\">—greeting=hi</emphasis> and 

"role=\"strong\">—debug</emphasis> options through the command-line. "

"In this example, <emphasis role=\"strong\">centos-art.sh</emphasis> "

"script executes a parent module named 

"\">hello</emphasis>, processes the module-specific options passed "

"through the command-line, prints a greeting message to standard "

"output and exits successfully."

msgid "Debugging execution of parent modules"

msgstr "Debugging execution of parent modules"

#, no-wrap

msgid ""

"Thu 10 Oct 2013 11:53:28 PM CDT =========================>      [0] | main\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_BASEDIR             Automation/Modules\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_NAME                [0]=hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_TYPE                parent\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_ARGUMENT            --greeting=hi\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_LIST                hello|help|locale|prepare|render|tuneup|vcs\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR                 Automation/Modules/Hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MODULES         Automation/Modules/Hello/Modules\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MANUALS         Automation/Modules/Hello/Manuals\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_LOCALES         Automation/Modules/Hello/Locales\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_CONFIGS         Automation/Modules/Hello/Configs\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_INIT_FILE           Automation/Modules/Hello/hello.sh\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAIN                      hello.sh\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAINDIR                   Automation/Modules/Hello/Locales\n"

"Thu 10 Oct 2013 11:53:28 PM CDT export -f                       hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT export -f                       hello_getOptions\n"

"Thu 10 Oct 2013 11:53:28 PM CDT ------------------------->      hello --greeting=hi\n"

"hi\n"

"Thu 10 Oct 2013 11:53:28 PM CDT <-------------------------      hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT unset -f                        hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT unset -f                        hello_getOptions\n"

"Thu 10 Oct 2013 11:53:28 PM CDT <=========================      [0] | main"

msgstr ""

"Thu 10 Oct 2013 11:53:28 PM CDT =========================>      [0] | main\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_BASEDIR             Automation/Modules\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_NAME                [0]=hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_TYPE                parent\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_ARGUMENT            --greeting=hi\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_LIST                hello|help|locale|prepare|render|tuneup|vcs\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR                 Automation/Modules/Hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MODULES         Automation/Modules/Hello/Modules\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MANUALS         Automation/Modules/Hello/Manuals\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_LOCALES         Automation/Modules/Hello/Locales\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_CONFIGS         Automation/Modules/Hello/Configs\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_INIT_FILE           Automation/Modules/Hello/hello.sh\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAIN                      hello.sh\n"

"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAINDIR                   Automation/Modules/Hello/Locales\n"

"Thu 10 Oct 2013 11:53:28 PM CDT export -f                       hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT export -f                       hello_getOptions\n"

"Thu 10 Oct 2013 11:53:28 PM CDT ------------------------->      hello --greeting=hi\n"

"hi\n"

"Thu 10 Oct 2013 11:53:28 PM CDT <-------------------------      hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT unset -f                        hello\n"

"Thu 10 Oct 2013 11:53:28 PM CDT unset -f                        hello_getOptions\n"

"Thu 10 Oct 2013 11:53:28 PM CDT <=========================      [0] | main"

msgid ""

"<xref linkend=\"debug-parent-modules\"/> describes an entire module "

"environment in action. With this information you can create your "

"own module environment, already. However, when your module is "

"getting too much complicated you probably want to divide it in "

"smaller pieces that you can execute accordingly, based on the "

"purpose you defined for it. Such kind of division can be "

"implemented as described in <xref linkend=\"module-optimization\"/>."

msgstr ""

"<xref linkend=\"debug-parent-modules\"/> describes an entire module "

"environment in action. With this information you can create your "

"own module environment, already. However, when your module is "

"getting too much complicated you probably want to divide it in "

"smaller pieces that you can execute accordingly, based on the "

"purpose you defined for it. Such kind of division can be "

"implemented as described in <xref linkend=\"module-optimization\"/>."

msgid "Summary"

msgstr "Summary"

msgid ""

"This section has covered basic concepts related to module "

"environment inside <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script. The next section takes these concepts and focuses "

"on the implementation of them. Once you finish it, you should be "

"able of writing your own module environments from scratch inside "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script."

msgstr ""

"This section has covered basic concepts related to module "

"environment inside <emphasis role=\"strong\">centos-art.sh</"

"emphasis> script. The next section takes these concepts and focuses "

"on the implementation of them. Once you finish it, you should be "

"able of writing your own module environments from scratch inside "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script."

msgid "Module Implementation"

msgstr "Module Implementation"

msgid ""

"The <emphasis role=\"strong\">centos-art.sh</emphasis> script "

"implements module environments inside the “<literal>Modules</"

"literal>” directory, as described in 

"structure\"/>."

msgstr ""

"The <emphasis role=\"strong\">centos-art.sh</emphasis> script "

"implements module environments inside the “<literal>Modules</"

"literal>” directory, as described in 

"structure\"/>."

msgid ""

"For example, consider the creation of a module named 

"\"strong\">hello</emphasis>. The purpose of this module is to print "

"a greeting message to standard output and then exit successfully. "

"To create such a module, we need to create a directory named "

"“Hello” inside the “Modules” directory and put an initialization "

"file named “hello.sh” inside it. Because we want to execute the "

"<emphasis role=\"strong\">hello</emphasis> module from 

"role=\"strong\">centos-art.sh</emphasis> script command-line, we "

"put it in the first level of directories of <literal>Modules</"

"literal> directory. See <xref linkend=\"parent-module-layout\"/>."

msgstr ""

"For example, consider the creation of a module named 

"\"strong\">hello</emphasis>. The purpose of this module is to print "

"a greeting message to standard output and then exit successfully. "

"To create such a module, we need to create a directory named "

"“Hello” inside the “Modules” directory and put an initialization "

"file named “hello.sh” inside it. Because we want to execute the "

"<emphasis role=\"strong\">hello</emphasis> module from 

"role=\"strong\">centos-art.sh</emphasis> script command-line, we "

"put it in the first level of directories of <literal>Modules</"

"literal> directory. See <xref linkend=\"parent-module-layout\"/>."

msgid "Directory layout used by parent modules"

msgstr "Directory layout used by parent modules"

#, no-wrap

msgid ""

".\n"

"|-- COPYING                     <co id=\"CO1-1\"></co>\n"

"|-- Locales/                    <co id=\"CO1-2\"></co>\n"

"|-- Manuals/                    <co id=\"CO1-3\"></co>\n"

"|-- Modules/                    <co id=\"CO1-4\"></co>\n"

"|   `-- Hello/                  <co id=\"CO1-5\"></co>\n"

"|       |-- hello.sh            <co id=\"CO1-6\"></co>\n"

"|       `-- hello_getOptions.sh <co id=\"CO1-7\"></co>\n"

"|-- Scripts/                    <co id=\"CO1-8\"></co>\n"

"|-- centos-art.conf.sh          <co id=\"CO1-9\"></co>\n"

"`-- centos-art.sh               <co id=\"CO1-10\"></co>"

msgstr ""

".\n"

"|-- COPYING                     <co id=\"CO1-1\"></co>\n"

"|-- Locales/                    <co id=\"CO1-2\"></co>\n"

"|-- Manuals/                    <co id=\"CO1-3\"></co>\n"

"|-- Modules/                    <co id=\"CO1-4\"></co>\n"

"|   `-- Hello/                  <co id=\"CO1-5\"></co>\n"

"|       |-- hello.sh            <co id=\"CO1-6\"></co>\n"

"|       `-- hello_getOptions.sh <co id=\"CO1-7\"></co>\n"

"|-- Scripts/                    <co id=\"CO1-8\"></co>\n"

"|-- centos-art.conf.sh          <co id=\"CO1-9\"></co>\n"

"`-- centos-art.sh               <co id=\"CO1-10\"></co>"

msgid "Script's copying conditions."

msgstr "Script's copying conditions."

msgid "Script's localization files."

msgstr "Script's localization files."

msgid "Script's documentation files."

msgstr "Script's documentation files."

msgid "Script's modules. Here is where you store parent modules."

msgstr "Script's modules. Here is where you store parent modules."

msgid "Parent directory of module named hello."

msgstr "Parent directory of module named hello."

msgid "Initialization file of module named hello."

msgstr "Initialization file of module named hello."

msgid "Function related to module named hello."

msgstr "Function related to module named hello."

msgid "Script's global functions."

msgstr "Script's global functions."

msgid "Script's configuration file."

msgstr "Script's configuration file."

msgid "Script's initialization file."

msgstr "Script's initialization file."

msgid ""

"<xref linkend=\"parent-module-layout\"/> presents a complete module "

"layout you can use as reference to create your own module "

"implementations. However, it is not complete yet. At this point, "

"when you execute <emphasis role=\"strong\">centos-art.sh</"

"emphasis>, it is able to find out <emphasis role=\"strong\">hello</"

"emphasis> module's initialization file and execute it but that "

"prints an error message because the initialization file doesn't "

"have a function definition inside. It is completely empty. In order "

"for <emphasis role=\"strong\">centos-art.sh</emphasis> script to do "

"something useful, you need to write a function definition inside "

"the initialization file, as described in 

"init-file\"/>."

msgstr ""

"<xref linkend=\"parent-module-layout\"/> presents a complete module "

"layout you can use as reference to create your own module "

"implementations. However, it is not complete yet. At this point, "

"when you execute <emphasis role=\"strong\">centos-art.sh</"

"emphasis>, it is able to find out <emphasis role=\"strong\">hello</"

"emphasis> module's initialization file and execute it but that "

"prints an error message because the initialization file doesn't "

"have a function definition inside. It is completely empty. In order "

"for <emphasis role=\"strong\">centos-art.sh</emphasis> script to do "

"something useful, you need to write a function definition inside "

"the initialization file, as described in 

"init-file\"/>."

msgid "The Initialization File"

msgstr "The Initialization File"

msgid ""

"The module's initialization file contains the module's main "

"function definition and a comment describing what it does on top of "

"it. This comment includes a small description about what the "

"function does, a written by section, the copyright note and the "

"legal status of the file. The function definition is set later and "

"must be written using the long definition format (i.e., it must "

"begin with the word “<literal>function</literal>,” then the "

"function name, and finally the “<literal>{</literal>” character). "

"The name of the function is exactly the same of the initialization "

"file but without the <literal>.sh</literal> extension. These "

"conditions are required in order for 

"\">centos-art.sh</emphasis> script to execute the function "

"definition and destroy it when it is no longer used. See 

"linkend=\"initialization-file\"/>."

msgstr ""

"The module's initialization file contains the module's main "

"function definition and a comment describing what it does on top of "

"it. This comment includes a small description about what the "

"function does, a written by section, the copyright note and the "

"legal status of the file. The function definition is set later and "

"must be written using the long definition format (i.e., it must "

"begin with the word “<literal>function</literal>,” then the "

"function name, and finally the “<literal>{</literal>” character). "

"The name of the function is exactly the same of the initialization "

"file but without the <literal>.sh</literal> extension. These "

"conditions are required in order for 

"\">centos-art.sh</emphasis> script to execute the function "

"definition and destroy it when it is no longer used. See 

"linkend=\"initialization-file\"/>."

msgid ""

"The function definition is where you write all the commands you "

"want the module runs, once executed. The function definition can be "

"as simple as just one single line of code or as complex as you can "

"imagine. It is the place where you express your solutions. However, "

"when writing initialization files, it is considered a good practice "

"to avoid any sort of complexity. Instead, try to write small and "

"simple initialization files. In case you notice the initialization "

"file is growing up inevitably, you can reduce its code by "

"refactoring it. To do this, you can use resources like module "

"related functions and child modules. These resources are described "

"in <xref linkend=\"module-optimization\"/>, and they help you to "

"keep the initialization file in a clean state, easy to understand, "

"maintain and debug."

msgstr ""

"The function definition is where you write all the commands you "

"want the module runs, once executed. The function definition can be "

"as simple as just one single line of code or as complex as you can "

"imagine. It is the place where you express your solutions. However, "

"when writing initialization files, it is considered a good practice "

"to avoid any sort of complexity. Instead, try to write small and "

"simple initialization files. In case you notice the initialization "

"file is growing up inevitably, you can reduce its code by "

"refactoring it. To do this, you can use resources like module "

"related functions and child modules. These resources are described "

"in <xref linkend=\"module-optimization\"/>, and they help you to "

"keep the initialization file in a clean state, easy to understand, "

"maintain and debug."

msgid "Initialization file used by hello module"

msgstr "Initialization file used by hello module"

#, no-wrap

msgid ""

"#!/bin/bash\n"

"######################################################################\n"

"#\n"

"#   hello.sh -- Print out greetings to standard output and exit\n"

"#   successfully.\n"

"#\n"

"#   Written by:\n"

"#   * Alain Reguera Delgado <al@centos.org.cu>, 2013\n"

"#\n"

"# Copyright (C) 2009-2013 The CentOS Artwork SIG\n"

"#\n"

"# This program is free software; you can redistribute it and/or modify\n"

"# it under the terms of the GNU General Public License as published by\n"

"# the Free Software Foundation; either version 2 of the License, or (at\n"

"# your option) any later version.\n"

"#\n"

"# This program is distributed in the hope that it will be useful, but\n"

"# WITHOUT ANY WARRANTY; without even the implied warranty of\n"

"# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU\n"

"# General Public License for more details.\n"

"#\n"

"# You should have received a copy of the GNU General Public License\n"

"# along with this program; if not, write to the Free Software\n"

"# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n"

"#\n"

"######################################################################\n"

"\n"

"function hello {\n"

"\n"

"    tcar_printMessage \"`gettext \"Hello, World!\"`\" --as-stdout-line\n"

"\n"

"}"

msgstr ""

"#!/bin/bash\n"

"######################################################################\n"

"#\n"

"#   hello.sh -- Print out greetings to standard output and exit\n"

"#   successfully.\n"

"#\n"

"#   Written by:\n"

"#   * Alain Reguera Delgado <al@centos.org.cu>, 2013\n"

"#\n"

"# Copyright (C) 2009-2013 The CentOS Artwork SIG\n"

"#\n"

"# This program is free software; you can redistribute it and/or modify\n"

"# it under the terms of the GNU General Public License as published by\n"

"# the Free Software Foundation; either version 2 of the License, or (at\n"

"# your option) any later version.\n"

"#\n"

"# This program is distributed in the hope that it will be useful, but\n"

"# WITHOUT ANY WARRANTY; without even the implied warranty of\n"

"# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU\n"

"# General Public License for more details.\n"

"#\n"

"# You should have received a copy of the GNU General Public License\n"

"# along with this program; if not, write to the Free Software\n"

"# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n"

"#\n"

"######################################################################\n"

"\n"

"function hello {\n"

"\n"

"    tcar_printMessage \"`gettext \"Hello, World!\"`\" --as-stdout-line\n"

"\n"

"}"

msgid ""

"The function definition described in 

"file\"/> uses the <emphasis role=\"strong\">tcar_printMessage</"

"emphasis> global function to print localized versions of the string "

"“Hello, World!” to standard output. Because there isn't no other "

"command in the function definition, when the greeting message is "

"printed out, <emphasis role=\"strong\">centos-art.sh</emphasis> "

"destroys the <emphasis role=\"strong\">hello</emphasis> module and "

"exit successfully. This process is more visible when also pass the "

"<emphasis role=\"strong\">—debug</emphasis> option. See 

"linkend=\"debug-parent-modules\"/>."

msgstr ""

"The function definition described in 

"file\"/> uses the <emphasis role=\"strong\">tcar_printMessage</"

"emphasis> global function to print localized versions of the string "

"“Hello, World!” to standard output. Because there isn't no other "

"command in the function definition, when the greeting message is "

"printed out, <emphasis role=\"strong\">centos-art.sh</emphasis> "

"destroys the <emphasis role=\"strong\">hello</emphasis> module and "

"exit successfully. This process is more visible when also pass the "

"<emphasis role=\"strong\">—debug</emphasis> option. See 

"linkend=\"debug-parent-modules\"/>."

msgid ""

"Congratulations! You've implemented a module environment inside "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script. With the "

"information you have so far, you are able to create your own module "

"environment implementations. The next section delves into available "

"resources you can use to simplify module environments when the "

"initialization file starts growing inevitably and complexity "

"daemons begin hammering your head."

msgstr ""

"Congratulations! You've implemented a module environment inside "

"<emphasis role=\"strong\">centos-art.sh</emphasis> script. With the "

"information you have so far, you are able to create your own module "

"environment implementations. The next section delves into available "

"resources you can use to simplify module environments when the "

"initialization file starts growing inevitably and complexity "

"daemons begin hammering your head."

msgid "Module Optimization"

msgstr "Module Optimization"

msgid ""

"The <emphasis role=\"strong\">centos-art.sh</emphasis> script "

"provides four resources you can use to optimize your module "

"implementations. These resources are “related functions,” “child "

"modules,” “sibling modules” and “recursive modules”."

msgstr ""

"The <emphasis role=\"strong\">centos-art.sh</emphasis> script "

"provides four resources you can use to optimize your module "

"implementations. These resources are “related functions,” “child "

"modules,” “sibling modules” and “recursive modules”."

msgid "Related Functions"

msgstr "Related Functions"

msgid ""

"Related functions are very useful when you need to simplify the "

"function definition of one initialization file. For example, "

"consider extending the <emphasis role=\"strong\">hello</emphasis> "

"module so it is able to interpret arguments passed through the "

"command-line. Now, inside the initialization file, we have some "

"variable definitions, one function call to a module related "

"function named <emphasis role=\"strong\">hello_getOptions</"

"emphasis>, and a decision on how the greeting message must be "

"printed out based on the collected actions. See 

"\"initialization-file-extended\"/>."

msgstr ""

"Related functions are very useful when you need to simplify the "

"function definition of one initialization file. For example, "

"consider extending the <emphasis role=\"strong\">hello</emphasis> "

"module so it is able to interpret arguments passed through the "

"command-line. Now, inside the initialization file, we have some "

"variable definitions, one function call to a module related "

"function named <emphasis role=\"strong\">hello_getOptions</"

"emphasis>, and a decision on how the greeting message must be "

"printed out based on the collected actions. See 

"\"initialization-file-extended\"/>."

msgid "Initialization file used by hello module (extended)"

msgstr "Initialization file used by hello module (extended)"

#, no-wrap

msgid ""

"function hello {\n"

"\n"

"    # Define default greeting message.\n"

"    local HELLO_WORLD=\"`gettext \"Hello, World!\"`\"\n"

"\n"

"    # Define actions variable. Here is where actions related to\n"

"    # module-specific options are stored in for further processing.\n"

"    local ACTIONS=''\n"

"\n"

"    # Interpret module-specific options and store related actions.\n"

"    hello_getOptions\n"

"\n"

"    # Print greeting message\n"

"    if [[ -z ${ACTIONS} ]];then\n"

"        # Using parent module.\n"

"        tcar_printMessage \"${HELLO_WORLD}\" --as-stdout-line\n"

"    else\n"

"        # Using child module.\n"

"        tcar_setModuleEnvironment -m 'output' -t 'child'\n"

"    fi\n"

"\n"

"}"

msgstr ""

"function hello {\n"

"\n"

"    # Define default greeting message.\n"

"    local HELLO_WORLD=\"`gettext \"Hello, World!\"`\"\n"

"\n"

"    # Define actions variable. Here is where actions related to\n"

"    # module-specific options are stored in for further processing.\n"

"    local ACTIONS=''\n"

"\n"

"    # Interpret module-specific options and store related actions.\n"

"    hello_getOptions\n"

"\n"

"    # Print greeting message\n"

"    if [[ -z ${ACTIONS} ]];then\n"

"        # Using parent module.\n"

"        tcar_printMessage \"${HELLO_WORLD}\" --as-stdout-line\n"

"    else\n"

"        # Using child module.\n"

"        tcar_setModuleEnvironment -m 'output' -t 'child'\n"

"    fi\n"

"\n"

"}"

msgid ""

"When you execute the command <emphasis role=\"strong\">centos-art."

"sh hello</emphasis> with the <emphasis role=\"strong\">—"

"greeting=hi</emphasis> argument, <emphasis role=\"strong\">centos-"

"art.sh</emphasis> stores module-specific arguments inside the "

"<literal>TCAR_MODULE_ARGUMENT</literal> variable, creates a list of "

"all function definitions inside the module directory and exports "

"them. This includes the function definition of the initialization "

"file itself. Then <emphasis role=\"strong\">centos-art.sh</"

"emphasis> executes the function definition set inside the "

"initialization file and leaves all other function definitions, "

"already in memory, waiting for further execution. At this point, "

"the <emphasis role=\"strong\">hello</emphasis> initialization "

"function sets some default values and execute the 

"\"strong\">hello_getOptions</emphasis> function to parse all the "

"arguments passed through the command-line and redefines the "

"<literal>ACTIONS</literal> variable based on them. Using the "

"<literal>ACTIONS</literal> variables it decides whether to print "

"the greeting message immediately or execute the child modules named "

"<emphasis role=\"strong\">output</emphasis> so it decides what to "

"do with the information collected so far."

msgstr ""

"When you execute the command <emphasis role=\"strong\">centos-art."

"sh hello</emphasis> with the <emphasis role=\"strong\">—"

"greeting=hi</emphasis> argument, <emphasis role=\"strong\">centos-"

"art.sh</emphasis> stores module-specific arguments inside the "

"<literal>TCAR_MODULE_ARGUMENT</literal> variable, creates a list of "

"all function definitions inside the module directory and exports "

"them. This includes the function definition of the initialization "

"file itself. Then <emphasis role=\"strong\">centos-art.sh</"

"emphasis> executes the function definition set inside the "

"initialization file and leaves all other function definitions, "

"already in memory, waiting for further execution. At this point, "

"the <emphasis role=\"strong\">hello</emphasis> initialization "

"function sets some default values and execute the 

"\"strong\">hello_getOptions</emphasis> function to parse all the "

"arguments passed through the command-line and redefines the "

"<literal>ACTIONS</literal> variable based on them. Using the "

"<literal>ACTIONS</literal> variables it decides whether to print "

"the greeting message immediately or execute the child modules named "

"<emphasis role=\"strong\">output</emphasis> so it decides what to "

"do with the information collected so far."

msgid ""

"<xref linkend=\"hello_getOptions-definition\"/> defines the options "

"you can pass to <emphasis role=\"strong\">hello</emphasis> module "

"and the associated actions they must perform for each of them. "

"Actions aren't immediately executed here. Instead, they are stored "

"in the <literal>ACTIONS</literal> variable for further processing "

"(e.g., we store the names of the modules we want to execute later). "

"The <literal>ACTIONS</literal> variable was defined in the "

"initialization file so it has a global scope inside the module "

"environment and is reachable from any related function executed "

"inside it. Storing the actions this way lets the 

"\"strong\">hello</emphasis> module to collect information about "

"different actions and execute them all in just one command. When "

"all options have been parsed, only non-option arguments remain in "

"the <literal>TCAR_MODULE_ARGUMENT</literal> variable."

msgstr ""

"<xref linkend=\"hello_getOptions-definition\"/> defines the options "

"you can pass to <emphasis role=\"strong\">hello</emphasis> module "

"and the associated actions they must perform for each of them. "

"Actions aren't immediately executed here. Instead, they are stored "

"in the <literal>ACTIONS</literal> variable for further processing "

"(e.g., we store the names of the modules we want to execute later). "

"The <literal>ACTIONS</literal> variable was defined in the "

"initialization file so it has a global scope inside the module "

"environment and is reachable from any related function executed "

"inside it. Storing the actions this way lets the 

"\"strong\">hello</emphasis> module to collect information about "

"different actions and execute them all in just one command. When "

"all options have been parsed, only non-option arguments remain in "

"the <literal>TCAR_MODULE_ARGUMENT</literal> variable."

msgid "Related function definition (hello_getOptions)"

msgstr "Related function definition (hello_getOptions)"

#, no-wrap

msgid ""

"function hello_getOptions {\n"

"\n"

"    # Define short options we want to support.\n"

"    local ARGSS=\"h::,v,g:,l,u,c,r\"\n"

"\n"

"    # Define long options we want to support.\n"

"    local ARGSL=\"help::,version,greeting:,lower,upper,camel,random\"\n"

"\n"

"    # Redefine arguments using getopt(1) command parser.\n"

"    tcar_setModuleArguments\n"

"\n"

"    # Reset positional parameters on this function, using output\n"

"    # produced from (getopt) arguments parser.\n"

"    eval set -- \"${TCAR_MODULE_ARGUMENT}\"\n"

"\n"

"    # Look for options passed through command-line.\n"

"    while true; do\n"

"        case \"${1}\" in\n"

"\n"

"            -h | --help )\n"

"                tcar_printHelp \"${2}\"\n"

"                ;;\n"

"\n"

"            -v | --version )\n"

"                tcar_printVersion \"${TCAR_MODULE_NAME}\"\n"

"                ;;\n"

"\n"

"            -g | --greeting )\n"

"                HELLO_WORLD=\"${2:-${HELLO_WORLD}}\"\n"

"                shift 2\n"

"                ;;\n"

"\n"

"            -l | --lower )\n"

"                ACTIONS=\"lower ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -u | --upper )\n"

"                ACTIONS=\"upper ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -c | --camel )\n"

"                ACTIONS=\"camel ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -r | --random )\n"

"                ACTIONS=\"random ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -- )\n"

"                shift 1\n"

"                break\n"

"                ;;\n"

"        esac\n"

"    done\n"

"\n"

"    # Redefine arguments using current positional parameters. Only\n"

"    # paths should remain as arguments, at this point.\n"

"    TCAR_MODULE_ARGUMENT=\"${@}\"\n"

"\n"

"}"

msgstr ""

"function hello_getOptions {\n"

"\n"

"    # Define short options we want to support.\n"

"    local ARGSS=\"h::,v,g:,l,u,c,r\"\n"

"\n"

"    # Define long options we want to support.\n"

"    local ARGSL=\"help::,version,greeting:,lower,upper,camel,random\"\n"

"\n"

"    # Redefine arguments using getopt(1) command parser.\n"

"    tcar_setModuleArguments\n"

"\n"

"    # Reset positional parameters on this function, using output\n"

"    # produced from (getopt) arguments parser.\n"

"    eval set -- \"${TCAR_MODULE_ARGUMENT}\"\n"

"\n"

"    # Look for options passed through command-line.\n"

"    while true; do\n"

"        case \"${1}\" in\n"

"\n"

"            -h | --help )\n"

"                tcar_printHelp \"${2}\"\n"

"                ;;\n"

"\n"

"            -v | --version )\n"

"                tcar_printVersion \"${TCAR_MODULE_NAME}\"\n"

"                ;;\n"

"\n"

"            -g | --greeting )\n"

"                HELLO_WORLD=\"${2:-${HELLO_WORLD}}\"\n"

"                shift 2\n"

"                ;;\n"

"\n"

"            -l | --lower )\n"

"                ACTIONS=\"lower ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -u | --upper )\n"

"                ACTIONS=\"upper ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -c | --camel )\n"

"                ACTIONS=\"camel ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -r | --random )\n"

"                ACTIONS=\"random ${ACTIONS}\"\n"

"                shift 1\n"

"                ;;\n"

"\n"

"            -- )\n"

"                shift 1\n"

"                break\n"

"                ;;\n"

"        esac\n"

"    done\n"

"\n"

"    # Redefine arguments using current positional parameters. Only\n"

"    # paths should remain as arguments, at this point.\n"

"    TCAR_MODULE_ARGUMENT=\"${@}\"\n"

"\n"

"}"

msgid ""

"<xref linkend=\"hello_getOptions-definition\"/> presents the "

"standard construction we use inside 

"\">centos-art.sh</emphasis> script for parsing arguments passed "

"through the command-line in a per-module basis. As convention, all "

"the parent modules you write must be able to interpret the "

"<emphasis role=\"strong\">—help</emphasis> and 

"\"strong\">—version</emphasis> options using the construction "

"described here."

msgstr ""

"<xref linkend=\"hello_getOptions-definition\"/> presents the "

"standard construction we use inside 

"\">centos-art.sh</emphasis> script for parsing arguments passed "

"through the command-line in a per-module basis. As convention, all "

"the parent modules you write must be able to interpret the "

"<emphasis role=\"strong\">—help</emphasis> and 

"\"strong\">—version</emphasis> options using the construction "

"described here."

msgid ""

"Related functions are very useful when you are refactoring the "

"initialization file of a module. However, they aren't so efficient "

"when you need to execute them at demand (e.g., based on specific "