'''pc-metapkgmanager''' is the back-end command line utility used by the PC-BSD® installer, System Manager, Update Manager, and Warden® to manage meta-packages. Meta-packages are like system components, and include supported and unsupported desktops, development utilities, hardware drivers, and miscellaneous applications such as MythTV or XBMC.

'''pc-metapkgmanager''' is the back-end command line utility used by the PC-BSD® installer, System Manager, Update Manager, and Warden® to manage meta-packages. Meta-packages are like system components, and include supported and unsupported desktops, development utilities, hardware drivers, and miscellaneous applications such as MythTV or XBMC.

+

<!--T:3-->

Beginning with version 9.1, PC-BSD® uses metapkgsets to determine which system components are available and which applications are installed with each system component. Currently, two metapkgsets are available: ''pcbsd'' which defines the available desktop components, and ''warden'' which defines the components available when creating a jail with Warden® or installing a PC-BSD® server. You can view the contents of these metapkgsets on {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/current#build-files/metapkgsets|txt=trac}}.

Beginning with version 9.1, PC-BSD® uses metapkgsets to determine which system components are available and which applications are installed with each system component. Currently, two metapkgsets are available: ''pcbsd'' which defines the available desktop components, and ''warden'' which defines the components available when creating a jail with Warden® or installing a PC-BSD® server. You can view the contents of these metapkgsets on {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/current#build-files/metapkgsets|txt=trac}}.

+

<!--T:4-->

The '''pc-metapkgmanager''' command can be used at the command line to install or delete meta-packages, update to the latest package set, or to change the default metapkgset. If you type the command without any options, it will display its usage:

The '''pc-metapkgmanager''' command can be used at the command line to install or delete meta-packages, update to the latest package set, or to change the default metapkgset. If you type the command without any options, it will display its usage:

−

'''pc-metapkgmanager'''

+

<!--T:5-->

−

usage: pc-metapkgmanager [options]

+

{{txtbox|box='''pc-metapkgmanager'''

−

Options:

+

usage: pc-metapkgmanager [options]

−

add pkg1,pkg2 <loc> -- Add the specified list of meta-packages

+

Options:

−

<loc> should be a FTP / HTTP url where pkg_add

+

&nbsp;add pkg1,pkg2 <loc> -- Add the specified list of meta-packages

−

can fetch packages, or an absolute path to

+

&nbsp; <loc> should be a FTP / HTTP url where pkg_add

−

location of pkg files on disk.

+

&nbsp; can fetch packages, or an absolute path to

−

checkup -- Check for updates to pkgs

+

&nbsp; location of pkg files on disk.

−

del pkg1,pkg2 -- Delete the specified list of meta-packages

+

&nbsp;checkup -- Check for updates to pkgs

−

list -- List the available meta-packages

+

&nbsp;del pkg1,pkg2 -- Delete the specified list of meta-packages

−

status <pkg> -- List the status of the specified meta-packages

+

&nbsp;list -- List the available meta-packages

−

update pkg,pkg2 <loc> -- Update system packages. Can use 'all' or <pkg,pkg2>.

+

&nbsp;status <pkg> -- List the status of the specified meta-packages

−

<loc> should be a FTP / HTTP url where pkg_add

+

&nbsp;update pkg,pkg2 <loc> -- Update system packages. Can use 'all' or <pkg,pkg2>.

−

can fetch packages, or an absolute path to

+

&nbsp; <loc> should be a FTP / HTTP url where pkg_add

−

location of pkg files on disk.

+

&nbsp; can fetch packages, or an absolute path to

−

--pkgset <pkgset> -- Change default pkgset we are using

+

&nbsp; location of pkg files on disk.

−

--chroot <dir> -- Operate on the directory specified using chroot

+

&nbsp;--pkgset <pkgset> -- Change default pkgset we are using

+

&nbsp;--chroot <dir> -- Operate on the directory specified using chroot}}

To permanently change the default metapkgset between ''pcbsd'' and ''warden'', modify the ''PCBSD_METAPKGSET'' variable in ''/usr/local/etc/pcbsd.conf''.

To permanently change the default metapkgset between ''pcbsd'' and ''warden'', modify the ''PCBSD_METAPKGSET'' variable in ''/usr/local/etc/pcbsd.conf''.

+

<!--T:12-->

To determine if a meta-package is installed, specify its "Meta Package" name as shown in the output of the '''pc-metapkgmanager list''' command. For example, to see if the Awesome desktop is installed:

To determine if a meta-package is installed, specify its "Meta Package" name as shown in the output of the '''pc-metapkgmanager list''' command. For example, to see if the Awesome desktop is installed:

−

'''pc-metapkgmanager status Awesome'''

+

<!--T:13-->

−

The meta-pkg Awesome is not installed

+

{{txtbox|box='''pc-metapkgmanager status Awesome'''

+

The meta-pkg Awesome is not installed}}

−

To install the meta-package, specify the meta-package name. The following example installs the Awesome meta-package. Only the superuser can install meta-packages. If you do not specify the URL, the default mirror will be used. If you receive an error, you can change the default mirror in Control Panel ➜ [[System Manager]] ➜ Mirrors.

+

<!--T:14-->

+

To install the meta-package, use the '''add''' option and specify the meta-package name. Only the superuser can install meta-packages. If you do not specify the URL, the default mirror will be used. If you receive an error when downloading the package, you can change the default mirror in ''Control Panel'' ➜ ''[[System Manager]]'' ➜ ''Mirrors''.

−

'''pc-metapkgmanager add Awesome

+

<!--T:15-->

−

Pending Meta-Package changes: 1

+

The following example installs the Awesome meta-package. '''pc-metapkgmanager''' will provide messages regarding the status of the installation:

−

Package source: NET

+

−

Preparing to add: Awesome...

+

−

Checking for updates to old packages...

+

−

Installing Meta-Package: Awesome

+

−

Getting package list...

+

−

Pending package changes: 6

+

−

Downloading package: awesome-3.4.13

+

+

<!--T:16-->

+

{{txtbox|box='''pc-metapkgmanager add Awesome'''

+

Pending Meta-Package changes: 1

+

Package source: NET

+

Preparing to add: Awesome...

+

Checking for updates to old packages...

+

Installing Meta-Package: Awesome

+

Getting package list...

+

Pending package changes: 6

+

Downloading package: awesome-3.4.13

+

//usr/local/tmp/awesome-3.4.13.txz 100% of 704 kB 637 kBps

+

Downloading package: libev-4.11,1

+

//usr/local/tmp/libev-4.11,1.txz 100% of 117 kB 361 kBps

+

Downloading package: libxdg-basedir-1.1.1

+

//usr/local/tmp/libxdg-basedir-1.1.1.txz 100% of 11 kB 130 kBps

+

Downloading package: xcb-util-image-0.3.8

+

//usr/local/tmp/xcb-util-image-0.3.8.txz 100% of 18 kB 141 kBps

+

Downloading package: xcb-util-keysyms-0.3.8

+

//usr/local/tmp/xcb-util-keysyms-0.3.8.txz 100% of 8040 B 72 kBps

+

Downloading package: xcb-util-wm-0.3.8

+

//usr/local/tmp/xcb-util-wm-0.3.8.txz 100% of 35 kB 148 kBps

+

Installing package: awesome-3.4.13

+

Skipping installed package: libev-4.11,1

+

Skipping installed package: libxdg-basedir-1.1.1

+

Skipping installed package: xcb-util-image-0.3.8

+

Skipping installed package: xcb-util-keysyms-0.3.8

+

Skipping installed package: xcb-util-wm-0.3.8

+

The meta-pkg Awesome is installed

+

Finished Meta-Package: Awesome

+

Meta-Package changes finished!}}

−

To delete an installed meta-package, specify its name. Only the superuser can uninstall meta-packages.

+

<!--T:17-->

+

To delete an installed meta-package, specify its name. Only the superuser can uninstall meta-packages. As seen in the following example, '''pc-metapkgmanager''' automatically determines which dependent packages are still needed by other applications and which can be safely removed.

−

'''pc-metapkgmanager del Awesome'''

+

<!--T:18-->

−

Pending Meta-Package changes: 1

+

{{txtbox|box='''pc-metapkgmanager del Awesome'''

−

Removing Meta-Package: Awesome

+

Pending Meta-Package changes: 1

−

Pending package changes: 1

+

Removing Meta-Package: Awesome

−

Removing: awesome-3.4.11_1

+

Getting package list...

−

The meta-pkg Awesome is not installed

+

Pending package changes: 66

−

Pruning unused packages... This may take a while...

+

Removing: awesome-3.4.13

−

Meta-Package changes finished!

+

Skipping Meta-Required: giflib-4.2.0_2

+

Removing: libev-4.11,1

+

Removing: libxdg-basedir-1.1.1

+

Removing: xcb-util-image-0.3.8

+

Removing: xcb-util-keysyms-0.3.8

+

Removing: xcb-util-wm-0.3.8

+

Skipping Required: bitstream-vera-1.10_5

+

Skipping Required: cairo-1.10.2_4,2

+

<snip output of other required packages>

+

The meta-pkg Awesome is not installed

+

Meta-Package changes finished!}}

−

'''pc-metapkgmanager''' can also be used to upgrade the packages that came with the operating system. When you run the '''pc-metapkgmanager list | more''' command, the "base-system" meta-package lists these packages. To determine if any are out-of-date:

+

=== Upgrading Meta-Packages === <!--T:19-->

−

'''pc-metapkgmanager status base-system'''

+

<!--T:20-->

−

??The meta-pkg base-system is partially installed??

+

'''pc-metapkgmanager''' can also be used to determine if any meta-packages are out of date and to update meta-packages. To determine if any meta-packages have newer versions:

−

??To update the out-of-date base packages, run the following command as the superuser:??

In this example, all meta-packages are at their latest versions. If any were out of date, you would instead receive the message "The following package updates are available:" followed by the names of the out-of-date meta-packages.

+

<!--T:23-->

+

To update a meta-package, use the '''pc-metapkgmanager update''' command followed by the name of the specific meta-package or the word '''all''' to update all out-of-date meta-packages.

Revision as of 21:19, 23 April 2013

(Sorry for the inconvenience)

Editor: please update template:UseTOC/9.2

Translator: please use {{UseTOC{{putVers}}|TOC}}

Protection (edit): sysopEdited by: Tigersharke

pc-metapkgmanager is the back-end command line utility used by the PC-BSD® installer, System Manager, Update Manager, and Warden® to manage meta-packages. Meta-packages are like system components, and include supported and unsupported desktops, development utilities, hardware drivers, and miscellaneous applications such as MythTV or XBMC.

Beginning with version 9.1, PC-BSD® uses metapkgsets to determine which system components are available and which applications are installed with each system component. Currently, two metapkgsets are available: pcbsd which defines the available desktop components, and warden which defines the components available when creating a jail with Warden® or installing a PC-BSD® server. You can view the contents of these metapkgsets on trac[1].

The pc-metapkgmanager command can be used at the command line to install or delete meta-packages, update to the latest package set, or to change the default metapkgset. If you type the command without any options, it will display its usage:

pc-metapkgmanager

usage: pc-metapkgmanager [options]
Options:
add pkg1,pkg2 <loc> -- Add the specified list of meta-packages
<loc> should be a FTP / HTTP url where pkg_add
can fetch packages, or an absolute path to
location of pkg files on disk.
checkup -- Check for updates to pkgs
del pkg1,pkg2 -- Delete the specified list of meta-packages
list -- List the available meta-packages
status <pkg> -- List the status of the specified meta-packages
update pkg,pkg2 <loc> -- Update system packages. Can use 'all' or <pkg,pkg2>.
<loc> should be a FTP / HTTP url where pkg_add
can fetch packages, or an absolute path to
location of pkg files on disk.
--pkgset <pkgset> -- Change default pkgset we are using

To permanently change the default metapkgset between pcbsd and warden, modify the PCBSD_METAPKGSET variable in /usr/local/etc/pcbsd.conf.

To determine if a meta-package is installed, specify its "Meta Package" name as shown in the output of the pc-metapkgmanager list command. For example, to see if the Awesome desktop is installed:

pc-metapkgmanager status Awesome
The meta-pkg Awesome is not installed

To install the meta-package, use the add option and specify the meta-package name. Only the superuser can install meta-packages. If you do not specify the URL, the default mirror will be used. If you receive an error when downloading the package, you can change the default mirror in Control Panel ➜ System Manager ➜ Mirrors.

The following example installs the Awesome meta-package. pc-metapkgmanager will provide messages regarding the status of the installation:

To delete an installed meta-package, specify its name. Only the superuser can uninstall meta-packages. As seen in the following example, pc-metapkgmanager automatically determines which dependent packages are still needed by other applications and which can be safely removed.

Upgrading Meta-Packages

pc-metapkgmanager can also be used to determine if any meta-packages are out of date and to update meta-packages. To determine if any meta-packages have newer versions:

pc-metapkgmanager checkup
All packages are up to date!

In this example, all meta-packages are at their latest versions. If any were out of date, you would instead receive the message "The following package updates are available:" followed by the names of the out-of-date meta-packages.

To update a meta-package, use the pc-metapkgmanager update command followed by the name of the specific meta-package or the word all to update all out-of-date meta-packages.