3.1.2 Packages Section

The %packages section defines the packages to be installed on the system, for example:

%packages
@base
@client-mgmt-tools
@core
@debugging
@basic-desktop
@desktop-debugging
@desktop-platform
@directory-client
@general-desktop
@graphical-admin-tools
@identity-management-server
@input-methods
@internet-browser
@java-platform
@legacy-x
@network-file-system-client
@network-tools
@perl-runtime
@print-client
@remote-desktop-clients
@security-tools
@server-platform
@server-policy
@system-admin-tools
@x11
mtools
pax
python-dmidecode
oddjob
wodim
sgpio
genisoimage
device-mapper-persistent-data
abrt-gui
samba-winbind
certmonger
openldap-clients
pam_krb5
krb5-workstation
ldapjdk
slapi-nis
libXmu
perl-DBD-SQLite
perl-Mozilla-LDAP
%end

Package group names start with a @ character. You can use the yum grouplist command on an existing Oracle Linux server to display both the installed package groups and the package groups that are available to install.

Individual packages to be installed are named without the @ prefix. If you specify a - character as a prefix, the package is not installed.

The %packages keyword takes the following options:

--ignoredeps

Installs the packages without attempting to fix any unresolved dependencies.

--ignoremissing

Installs the available packages without prompting about missing packages. By default, kickstart interrupts the installation and asks you whether you want to continue the installation.

--resolvedeps

Install the packages and prompt if there are any unresolved dependencies.

You can also use a package list that is available as a local file in kickstart's ramdisk file system or that is accessible on an HTTP server, for example:

%packages --ignoremissing
%include /tmp/package-list
%end