aboutsummaryrefslogtreecommitdiffstats
path: root/Changes
diff options
context:
space:
mode:
authorPascal Terjan <pterjan@mageia.org>2022-10-25 20:29:46 +0000
committerPascal Terjan <pterjan@mageia.org>2022-11-01 22:23:53 +0000
commit2c86ed6389d741cfe41323937e9e93b89935490e (patch)
tree046cb4f3b1bf2046d8555ae18100280c3a3fb62c /Changes
parent775e1ad51b6318b1a308be9b997accc470329282 (diff)
downloadperl-URPM-topic/parse_property.tar
perl-URPM-topic/parse_property.tar.gz
perl-URPM-topic/parse_property.tar.bz2
perl-URPM-topic/parse_property.tar.xz
perl-URPM-topic/parse_property.zip
Fix parsing of properties containing [topic/parse_property
For example, the name extracted from a requirement of "python3.10dist(fonttools[unicode])[>= 4.10]" was sometimes "python3.10dist(fonttools" instead of the expected "python3.10dist(fonttools[unicode])". Code parsing such strings existed in many places, it now exists only in 2 places, a perl version in Resolve.pm and a C version in URPM.xs. Both codes used to handle both "foo >= 0" and "foo[>= 0]" but at least the perl code seems to only call it on provides/conflicts/obsoletes which are always using the second form so the support for it was dropped from the perl version for the sake of simplicity.
Diffstat (limited to 'Changes')
0 files changed, 0 insertions, 0 deletions