yum-filter-data(1)

1yum-filter-data(1)                                          yum-filter-data(1)
2
3
4

NAME

6       yum filter data plugin
7

SYNOPSIS

9       yum [options] [command] [package ...]
10

DESCRIPTION

12       This  plugin extends yum with some options, currently just for "update"
13       and "list update" type commands, to allow filters to be placed on which
14       packages  should be used based on the data in those packages. Note that
15       due to some of the data being unknown, and thus could  possibly  match,
16       all unknown data is treated as a match.
17

GENERAL OPTIONS

19       These  are  the  options  added  to yum that are available in the "list
20       updates", "info updates", "check-update" and  "update"  commands.  They
21       are:
22
23       --filter-vendors
24              This  option includes packages which have a vendor which matches
25              one of the passed vendor wildcard strings, or is  unknown.  Note
26              that  vendors can have spaces in their value, so "," is the only
27              way to specify multiple vendors as one option argument.
28
29       --filter-rpm-groups
30              This option includes packages which have a group  which  matches
31              one  of  the  passed  rpm group wildcard strings, or is unknown.
32              Note that rpm groups can have spaces in their value, so  ","  is
33              the  only way to specify multiple rpm groups as one option argu‐
34              ment.
35
36       --filter-packagers
37              This option  includes  packages  which  have  a  packager  which
38              matches  one  of  the  passed  packager  wildcard strings, or is
39              unknown. Note that vendors can have spaces in  their  value,  so
40              ","  is the only way to specify multiple packagers as one option
41              argument.
42
43       --filter-licenses
44              This option includes packages which have a license which matches
45              one  of the passed license wildcard strings, or is unknown. Note
46              that licenses can have spaces in their value, so "," is the only
47              way to specify multiple licenses as one option argument.
48
49       --filter-arches
50              This  option  includes  packages which have a arch which matches
51              one of the passed arch wildcard strings, or is unknown.
52
53       --filter-committers
54              This option includes  packages  which  have  a  committer  which
55              matches  one  of  the  passed  committer wildcard strings, or is
56              unknown. Note that committers can have spaces in their value, so
57              "," is the only way to specify multiple committers as one option
58              argument. Also, committer values are so loosely formed that they
59              could  contain  commas too, it is recommended to not do that but
60              you can work around it by using "?".
61
62       --filter-buildhosts
63              This option includes  packages  which  have  a  buildhost  which
64              matches  one  of  the  passed  buildhost wildcard strings, or is
65              unknown.
66
67       --filter-urls
68              This option includes packages which have a url which matches one
69              of the passed url wildcard strings, or is unknown.
70
71       --filter-package-sizes
72              This  option includes packages which have a packagesize which is
73              within one of the passed packagesize ranges, or is unknown.
74
75       --filter-archive-sizes
76              This option includes packages which have a archivesize which  is
77              within one of the passed archivesize ranges, or is unknown.
78
79       --filter-installed-sizes
80              This  option  includes packages which have a installedsize which
81              is within one of the passed installedsize ranges, or is unknown.
82
83       --filter-groups
84              This option includes packages which are in  a  yum  group  which
85              matches  one  of the passed yum group id strings, or is unknown.
86              Note that yum groups can have spaces in their value, so  ","  is
87              the  only way to specify multiple yum groups as one option argu‐
88              ment.
89

EXAMPLES

91       To list all updates that are 1 MB or less use:
92
93              yum --filter-package-sizes=-1m check-update
94
95       To apply updates that Dan Walsh has committed use:
96
97              yum --filter-committers='Dan Walsh *' update
98
99       To list updates for a specific group use:
100
101              yum --filter-rpm-groups='App*/Sys*' list updates
102
103       To apply updates to a specific set of groups use:
104
105              yum --filter-rpm-groups='App*/System,Devel*/Lib*,System Environ‐
106              ment/Base' update
107
108       To list updates for a set of yum groups use:
109
110              yum   --filter-groups='PostgreSQL   Database,Web   Server'  list
111              updates
112
113       To apply updates to a specific set of yum groups use:
114
115              yum --filter-groups='KDE,Core,Printing Support' update
116
117

AUTHORS

125       James Antill <james.antill@redhat.com>.
126
127

BUGS

129       Currently yum can't filter packages in all  of  the  commands,  so  for
130       instance "yum list 'yum*'" doesn't get the results filtered.
131
132       Apart  from that there are no bugs, but should you find any, you should
133       first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if
134       unsuccessful  in  finding  a  resolution contact the mailing list: yum-
135       devel@lists.baseurl.org.  To file a bug use  http://bugzilla.redhat.com
136       for  Fedora/RHEL/Centos  related bugs and http://yum.baseurl.org/report
137       for all other bugs.
138
139
140
141
142James Antill                   04 February 2008             yum-filter-data(1)