The blacklist contains those patches that should be excluded during the patch set creation process. It also contains those patches that should be replaced by another patch. This list contains one patch per line, where patches are given a specific revision level, or the patch ID is given by itself. You can also replace a given patch. To do so, provide a second column with the replacement patch ID.
Be mindful that no further dependency checks are performed on the replacement patch.
As with the whitelist configuration, lines beginning with a hash mark (#) and empty lines are ignored. You can use selectors at the end of a line to indicate for which system the specified patch should be replaced or ignored. See the whitelist configuration information for possible selectors to use. The selector must be the last entry on a line. Values of the selectors that are embedded in slashes are treated as regular expressions. You can also list a patch multiple times, with different selectors. In this instance, the first match is taken as black-listed patch.
This is an example of a blacklist configuration.
# We don't like this patch at all: 123456 # We don't like this very specific revision # However, other revision could be included. 789098-24 # We want to replace a specific patch 109320-06 109320-08 # Only ignore this patch on machine "eclipse" 109456-13 name=>"eclipse" # Patches can be mentioned multiple times with different # selectors 109456-13 name=>"sun42" # The same as above in one single line using regular expressions 109456-13 name=>"/eclipse|sun42/" # Replace this patch on all Solaris 5.8 machines 109320-06 109320-08 os=>"Solaris",version=>"5.8" |
Any additional patches that are dependent on these black-listed patches are excluded from the resulting patch set, as well. For replacement patches, no further check or dependency resolution is performed. You can provide more than one blacklist option in the configuration file. Multiple blacklist entries are merged. If a blacklist cannot be found, it is ignored.