SUSE Package Hub 15 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-Standard-Pool
Package Hub 15
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-Standard-Pool
Package Hub 15
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP1 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP1-Backports-Pool
Package Hub 15 SP1
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP1 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP1-Backports-Pool
Package Hub 15 SP1
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP2 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP2-Backports-Pool
Package Hub 15 SP2
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP2 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP2-Backports-Pool
Package Hub 15 SP2
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP3 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP3-Backports-Pool
Package Hub 15 SP3
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP3 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP3-Backports-Pool
Package Hub 15 SP3
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP4 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP4-Backports-Pool
Package Hub 15 SP4
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP4 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP4-Backports-Pool
Package Hub 15 SP4
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP5 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP5-Standard-Pool
Package Hub 15 SP5
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose:
SUSE Package Hub 15 SP5 one-click install
Install perl-Config-GitLike
NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled.
See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension
If the extension is not enabled, this installation will fail while trying to enable an invalid repo.
This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered.
SUSE-PackageHub-15-SP5-Standard-Pool
Package Hub 15 SP5
Dummy repo - this will fail
-
perl-Config-GitLike
Git-Compatible Config File Parsing
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose: