# -*- perl -*- # Lintian::Relation -- operations on dependencies and relationships # Copyright (C) 1998 Christian Schwarz and Richard Braakman # Copyright (C) 2004-2009 Russ Allbery # # This program is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free # Software Foundation; either version 2 of the License, or (at your option) # any later version. # # This program is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # this program. If not, see . package Lintian::Relation; use strict; use warnings; use Lintian::Relation::Version; =head1 NAME Lintian::Relation - Lintian operations on dependencies and relationships =head1 SYNOPSIS my $depends = Lintian::Relation->new('foo | bar, baz'); print "yes\n" if $depends->implies('baz'); print "no\n" if $depends->implies('foo'); =head1 DESCRIPTION This module provides functions for parsing and evaluating package relationship fields such as Depends and Recommends for binary packages and Build-Depends for source packages. It parses a relationship into an internal format and can then answer questions such as "does this dependency require that a given package be installed" or "is this relationship a superset of another relationship." A dependency line is viewed as a predicate formula. The comma separator means "and", and the alternatives separator means "or". A bare package name is the predicate "a package of this name is available". A package name with a version clause is the predicate "a package of this name that satisfies this version clause is available." Architecture restrictions, as specified in Policy for build dependencies, are supported and also checked in the implication logic unless the new_noarch() constructor is used. With that constructor, architecture restrictions are ignored. =head1 CLASS METHODS =over 4 =item new(RELATION) Creates a new Lintian::Relation object corresponding to the parsed relationship RELATION. This object can then be used to ask questions about that relationship. RELATION may be C or the empty string, in which case the returned Lintian::Relation object is empty (always satisfied). =cut # The internal parser which converts a single package element of a # relationship into the parsed form used for later processing. We permit # substvars to be used as package names so that we can use these routines with # the unparsed debian/control file. sub parse_element { my ($class, $element) = @_; $element =~ / ^\s* # skip leading whitespace ( # package name or substvar (1) (?: # start of the name [a-zA-Z0-9][a-zA-Z0-9+.-]+ # start of a package name | # or \$\{[a-zA-Z0-9:-]+\} # substvar ) # end of start of the name (?: # substvars may be mixed in [a-zA-Z0-9+.-]+ # package name portion | # or \$\{[a-zA-Z0-9:-]+\} # substvar )* # zero or more portions or substvars ) # end of package name or substvar (?: # start of optional version \s* \( # open parenthesis for version part \s* (<<|<=|=|>=|>>|<|>) # relation part (2) \s* (.*?) # version (3) \s* \) # closing parenthesis )? # end of optional version (?: # start of optional architecture \s* \[ # open bracket for architecture \s* (.*?) # architectures (4) \s* \] # closing bracket )? # end of optional architecture /x; # If there's no version, we don't need to do any further processing. # Otherwise, convert the legacy < and > relations to the current ones. return ['PRED', $1, undef, undef, $4] if not defined $2; my $two = $2; if ($two eq '<') { $two = '<<'; } elsif ($two eq '>') { $two = '>>'; } return ['PRED', $1, $two, $3, $4]; } # Create a new Lintian::Relation object, parsing the argument into our # internal format. sub new { my ($class, $relation) = @_; $relation = '' unless defined($relation); my @result; for my $element (split(/\s*,\s*/o, $relation)) { next if $element eq ''; my @alternatives; for my $alternative (split(/\s*\|\s*/o, $element)) { push(@alternatives, $class->parse_element($alternative)); } if (@alternatives == 1) { push(@result, @alternatives); } else { push(@result, ['OR', @alternatives]); } } my $self; if (@result == 1) { $self = $result[0]; } else { $self = ['AND', @result]; } bless($self, $class); return $self; } =item new_noarch(RELATION) Creates a new Lintian::Relation object corresponding to the parsed relationship RELATION, ignoring architecture restrictions. This should be used in cases where we only care if a dependency is present in some cases and we don't want to require that the architectures match (such as when checking for proper build dependencies, since if there are architecture constraints the maintainer is doing something beyond Lintian's ability to analyze). RELATION may be C or the empty string, in which case the returned Lintian::Relation object is empty (always satisfied). =cut sub new_noarch { my ($class, $relation) = @_; $relation = '' unless defined($relation); $relation =~ s/\[[^\]]*\]//g; return $class->new($relation); } =back =head1 INSTANCE METHODS =over 4 =item duplicates() Returns a list of duplicated elements within the relation object. Each element of the returned list will be a reference to an anonymous array holding a set of relations considered duplicates of each other. Two relations are considered duplicates if one implies the other, meaning that if one relationship is satisfied, the other is necessarily satisfied. This relationship does not have to be commutative: the opposite implication may not hold. =cut sub duplicates { my ($self) = @_; # There are no duplicates unless the top-level relationship is AND. if ($self->[0] ne 'AND') { return (); } # The logic here is a bit complex in order to merge sets of duplicate # dependencies. We want foo (<< 2), foo (>> 1), foo (= 1.5) to end up as # one set of duplicates, even though the first doesn't imply the second. # # $dups holds a hash, where the key is the earliest dependency in a set # and the value is a hash whose keys are the other dependencies in the # set. $seen holds a map from package names to the duplicate sets that # they're part of, if they're not the earliest package in a set. If # either of the dependencies in a duplicate pair were already seen, add # the missing one of the pair to the existing set rather than creating a # new one. my (%dups, %seen); for (my $i = 1; $i < @$self; $i++) { for (my $j = $i + 1; $j < @$self; $j++) { my $forward = $self->implies_array($self->[$i], $self->[$j]); my $reverse = $self->implies_array($self->[$j], $self->[$i]); if ($forward or $reverse) { my $first = $self->unparse($self->[$i]); my $second = $self->unparse($self->[$j]); if ($seen{$first}) { $dups{$seen{$first}}->{$second} = $j; $seen{$second} = $seen{$first}; } elsif ($seen{$second}) { $dups{$seen{$second}}->{$first} = $i; $seen{$first} = $seen{$second}; } else { $dups{$first} ||= {}; $dups{$first}->{$second} = $j; $seen{$second} = $first; } } } } # The sort maintains the original order in which we encountered the # dependencies, just in case that helps the user find the problems, # despite the fact we're using a hash. return map { [ $_, sort { $dups{$_}->{$a} <=> $dups{$_}->{$b} } keys %{ $dups{$_} } ] } keys %dups; } =item implies(RELATION) Returns true if the relationship implies RELATION, meaning that if the Lintian::Relation object is satisfied, RELATION will always be satisfied. RELATION may be either a string or another Lintian::Relation object. By default, architecture restrictions are honored in RELATION if it is a string. If architecture restrictions should be ignored in RELATION, create a Lintian::Relation object with new_noarch() and pass that in as RELATION instead of the string. =cut # This internal function does the heavily lifting of comparing two # elements. # # Takes two elements and returns true iff the second can be deduced from the # first. If the second is falsified by the first (in other words, if p # actually implies not q), return 0. Otherwise, return undef. The 0 return # is used by implies_element_inverse. sub implies_element { my ($self, $p, $q) = @_; # If the names don't match, there is no relationship between them. $$p[1] = '' unless defined $$p[1]; $$q[1] = '' unless defined $$q[1]; return if $$p[1] ne $$q[1]; # If the names match, then the only difference is in the architecture or # version clauses. First, check architecture. The architectures for p # must be a superset of the architectures for q. my @p_arches = split(' ', defined($$p[4]) ? $$p[4] : ''); my @q_arches = split(' ', defined($$q[4]) ? $$q[4] : ''); if (@p_arches || @q_arches) { my $p_arch_neg = @p_arches && $p_arches[0] =~ /^!/; my $q_arch_neg = @q_arches && $q_arches[0] =~ /^!/; # If p has no arches, it is a superset of q and we should fall through # to the version check. if (not @p_arches) { # nothing } # If q has no arches, it is a superset of p and there are no useful # implications. elsif (not @q_arches) { return; } # Both have arches. If neither are negated, we know nothing useful # unless q is a subset of p. elsif (not $p_arch_neg and not $q_arch_neg) { my %p_arches = map { $_ => 1 } @p_arches; my $subset = 1; for my $arch (@q_arches) { $subset = 0 unless $p_arches{$arch}; } return unless $subset; } # If both are negated, we know nothing useful unless p is a subset of # q (and therefore has fewer things excluded, and therefore is more # general). elsif ($p_arch_neg and $q_arch_neg) { my %q_arches = map { $_ => 1 } @q_arches; my $subset = 1; for my $arch (@p_arches) { $subset = 0 unless $q_arches{$arch}; } return unless $subset; } # If q is negated and p isn't, we'd need to know the full list of # arches to know if there's any relationship, so bail. elsif (not $p_arch_neg and $q_arch_neg) { return; } # If p is negated and q isn't, q is a subset of p iff none of the # negated arches in p are present in q. elsif ($p_arch_neg and not $q_arch_neg) { my %q_arches = map { $_ => 1 } @q_arches; my $subset = 1; for my $arch (@p_arches) { $subset = 0 if $q_arches{substr($arch, 1)}; } return unless $subset; } } # Now, down to version. The implication is true if p's clause is stronger # than q's, or is equivalent. # If q has no version clause, then p's clause is always stronger. return 1 if not defined $$q[2]; # If q does have a version clause, then p must also have one to have any # useful relationship. return if not defined $$p[2]; # q wants an exact version, so p must provide that exact version. p # disproves q if q's version is outside the range enforced by p. if ($$q[2] eq '=') { if ($$p[2] eq '<<') { return versions_lte($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '<=') { return versions_lt($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '>>') { return versions_gte($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '>=') { return versions_gt($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '=') { return versions_equal($$p[3], $$q[3]); } } # A greater than clause may disprove a less than clause. Otherwise, if # p's clause is <<, <=, or =, the version must be <= q's to imply q. if ($$q[2] eq '<=') { if ($$p[2] eq '>>') { return versions_gte($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '>=') { return versions_gt($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '=') { return versions_lte($$p[3], $$q[3]); } else { return versions_lte($$p[3], $$q[3]) ? 1 : undef; } } # Similar, but << is stronger than <= so p's version must be << q's # version if the p relation is <= or =. if ($$q[2] eq '<<') { if ($$p[2] eq '>>' or $$p[2] eq '>=') { return versions_gte($$p[3], $$p[3]) ? 0 : undef; } elsif ($$p[2] eq '<<') { return versions_lte($$p[3], $$q[3]); } elsif ($$p[2] eq '=') { return versions_lt($$p[3], $$q[3]); } else { return versions_lt($$p[3], $$q[3]) ? 1 : undef; } } # Same logic as above, only inverted. if ($$q[2] eq '>=') { if ($$p[2] eq '<<') { return versions_lte($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '<=') { return versions_lt($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '=') { return versions_gte($$p[3], $$q[3]); } else { return versions_gte($$p[3], $$q[3]) ? 1 : undef; } } if ($$q[2] eq '>>') { if ($$p[2] eq '<<' or $$p[2] eq '<=') { return versions_lte($$p[3], $$q[3]) ? 0 : undef; } elsif ($$p[2] eq '>>') { return versions_gte($$p[3], $$q[3]); } elsif ($$p[2] eq '=') { return versions_gt($$p[3], $$q[3]); } else { return versions_gt($$p[3], $$q[3]) ? 1 : undef; } } return; } # This internal function does the heavy of AND, OR, and NOT logic. It expects # two references to arrays instead of an object and a relation. sub implies_array { my ($self, $p, $q) = @_; my $i; if ($q->[0] eq 'PRED') { if ($p->[0] eq 'PRED') { return $self->implies_element($p, $q); } elsif ($p->[0] eq 'AND') { $i = 1; while ($i < @$p) { return 1 if $self->implies_array($p->[$i++], $q); } return 0; } elsif ($p->[0] eq 'OR') { $i = 1; while ($i < @$p) { return 0 if not $self->implies_array($p->[$i++], $q); } return 1; } elsif ($p->[0] eq 'NOT') { return $self->implies_array_inverse($p->[1], $q); } } elsif ($q->[0] eq 'AND') { # Each of q's clauses must be deduced from p. $i = 1; while ($i < @$q) { return 0 if not $self->implies_array($p, $q->[$i++]); } return 1; } elsif ($q->[0] eq 'OR') { # If p is something other than OR, p needs to satisfy one of the # clauses of q. If p is an AND clause, q is satisfied if any of the # clauses of p satisfy it. # # The interesting case is OR. In this case, do an OR to OR comparison # to determine if q's clause is a superset of p's clause as follows: # take each branch of p and see if it satisfies a branch of q. If # each branch of p satisfies some branch of q, return 1. Otherwise, # return 0. # # Simple logic that requires that p satisfy at least one of the # clauses of q considered in isolation will miss that a|b satisfies # a|b|c, since a|b doesn't satisfy any of a, b, or c in isolation. if ($p->[0] eq 'PRED') { $i = 1; while ($i < @$q) { return 1 if $self->implies_array($p, $q->[$i++]); } return 0; } elsif ($p->[0] eq 'AND') { $i = 1; while ($i < @$p) { return 1 if $self->implies_array($p->[$i++], $q); } return 0; } elsif ($p->[0] eq 'OR') { for ($i = 1; $i < @$p; $i++) { my $j = 1; my $satisfies = 0; while ($j < @$q) { if ($self->implies_array($p->[$i], $q->[$j++])) { $satisfies = 1; last; } } return 0 unless $satisfies; } return 1; } elsif ($p->[0] eq 'NOT') { return $self->implies_array_inverse($p->[1], $q); } } elsif ($q->[0] eq 'NOT') { if ($p->[0] eq 'NOT') { return $self->implies_array($q->[1], $p->[1]); } return $self->implies_array_inverse($p, $q->[1]); } } # The public interface. sub implies { my ($self, $relation) = @_; if (ref($relation) ne 'Lintian::Relation') { $relation = Lintian::Relation->new($relation); } return $self->implies_array($self, $relation); } =item implies_inverse(RELATION) Returns true if the relationship implies that RELATION is certainly false, meaning that if the Lintian::Relation object is satisfied, RELATION cannot be satisfied. RELATION may be either a string or another Lintian::Relation object. As with implies(), by default, architecture restrictions are honored in RELATION if it is a string. If architecture restrictions should be ignored in RELATION, create a Lintian::Relation object with new_noarch() and pass that in as RELATION instead of the string. =cut # This internal function does the heavy lifting of inverse implication between # two elements. Takes two elements and returns true iff the falsehood of # the second can be deduced from the truth of the first. In other words, p # implies not q, or resstated, q implies not p. (Since if a implies b, not b # implies not a.) Due to the return value of implies_element(), we can let it # do most of the work. sub implies_element_inverse { my ($self, $p, $q) = @_; my $result = $self->implies_element($q, $p); return not $result if defined $result; return; } # This internal function does the heavily lifting for AND, OR, and NOT # handling for inverse implications. It takes two references to arrays and # returns true iff the falsehood of the second can be deduced from the truth # of the first. sub implies_array_inverse { my ($self, $p, $q) = @_; my $i; if ($$q[0] eq 'PRED') { if ($$p[0] eq 'PRED') { return $self->implies_element_inverse($p, $q); } elsif ($$p[0] eq 'AND') { # q's falsehood can be deduced from any of p's clauses $i = 1; while ($i < @$p) { return 1 if $self->implies_array_inverse($$p[$i++], $q); } return 0; } elsif ($$p[0] eq 'OR') { # q's falsehood must be deduced from each of p's clauses $i = 1; while ($i < @$p) { return 0 if not $self->implies_array_inverse($$p[$i++], $q); } return 1; } elsif ($$p[0] eq 'NOT') { return $self->implies_array($q, $$p[1]); } } elsif ($$q[0] eq 'AND') { # Any of q's clauses must be falsified by p. $i = 1; while ($i < @$q) { return 1 if $self->implies_array_inverse($p, $$q[$i++]); } return 0; } elsif ($$q[0] eq 'OR') { # Each of q's clauses must be falsified by p. $i = 1; while ($i < @$q) { return 0 if not $self->implies_array_inverse($p, $$q[$i++]); } return 1; } elsif ($$q[0] eq 'NOT') { return $self->implies_array($p, $$q[1]); } } # The public interface. sub implies_inverse { my ($self, $relation) = @_; if (ref($relation) ne 'Lintian::Relation') { $relation = Lintian::Relation->new($relation); } return $self->implies_array_inverse($self, $relation); } =item unparse() Returns the textual form of a relationship. This converts the internal form back into the textual representation and returns that, not the original argument, so the spacing is standardized. Returns undef on internal faliures (such as an object in an unexpected format). =cut # The second argument isn't part of the public API. It's a partial relation # that's not a blessed object and is used by unparse() internally so that it # can recurse. # # We also support a NOT predicate. This currently isn't ever generated by a # regular relation, but it may someday be useful. sub unparse { my ($self, $partial) = @_; my $relation = defined($partial) ? $partial : $self; if ($relation->[0] eq 'PRED') { my $text = $relation->[1]; if (defined $relation->[2]) { $text .= " ($relation->[2] $relation->[3])"; } if (defined $relation->[4]) { $text .= " [$relation->[4]]"; } return $text; } elsif ($relation->[0] eq 'AND' || $relation->[0] eq 'OR') { my $seperator = ($relation->[0] eq 'AND') ? ', ' : ' | '; my $text = ''; for my $element (@$relation[1 .. $#$relation]) { $text .= $seperator if $text; my $result = $self->unparse($element); return unless defined($result); $text .= $result; } return $text; } elsif ($relation->[0] eq 'NOT') { return '! ' . $self->unparse($relation->[1]); } else { return; } } =back =head1 AUTHOR Originally written by Russ Allbery for Lintian. =head1 SEE ALSO lintian(1) =cut 1; # Local Variables: # indent-tabs-mode: nil # cperl-indent-level: 4 # End: # vim: syntax=perl sw=4 sts=4 sr et