Skip to content

Commit 917fd35

Browse files
committed
Add documentation for yum group and install options
1 parent d8a759b commit 917fd35

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -264,13 +264,17 @@ rpm -q "$PACKAGE_NAME" --qf '%|EPOCH?{%{EPOCH}}:{0}|:%{NAME}-%{VERSION}-%{RELEAS
264264

265265
### Install or remove *yum* package group
266266

267+
Install yum [package groups](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sec-working_with_package_groups). To list groups: `yum group list`. Then use that name in your puppet manifest. With support for install_options (e.g. enable repos if disabled by default).
268+
267269
```puppet
268270
yum::group { 'X Window System':
269-
ensure => present,
270-
timeout => 600,
271+
ensure => present,
272+
timeout => 600,
273+
install_options => ['--enablerepo=*'];
271274
}
272275
```
273276

277+
274278
### Install or remove packages via `yum install`
275279

276280
This is a workaround for [PUP-3323](https://tickets.puppetlabs.com/browse/PUP-3323). It enables the installation of packages from non-repo sources while still providing dependency resolution. For example, say there is a package *foo* that requires the package *bar*. *bar* is in a Yum repository and *foo* is stored on a stand-alone HTTP server. Using the standard providers for the `Package` resource type, `rpm` and `yum`, the `rpm` provider would be required to install *foo*, because only it can install from a non-repo source, i.e., a URL. However, since the `rpm` provider cannot do dependency resolution, it would fail on its own unless *bar* was already installed. This workaround enables *foo* to be installed without having to define its dependencies in Puppet.

0 commit comments

Comments
 (0)