Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 572178 - sys-apps/portage-2.2.26 accepts non-PMS wildcard versions in config files
Summary: sys-apps/portage-2.2.26 accepts non-PMS wildcard versions in config files
Status: RESOLVED WONTFIX
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Configuration (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-17 09:18 UTC by Martin Väth
Modified: 2016-02-06 12:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Väth 2016-01-17 09:18:59 UTC
After the change to pms-compliant wildcard version specifications, I rewrote eix correspondingly, to receive now this bug report

https://github.com/vaeth/eix/issues/21

> 'man portage' "Wildcard Patterns" also verifies the syntax
> to be ok in the 'Examples' section:
> =*/*-*9999*

Indeed, it seems that e.g. =foo/bar-*9* is accepted in /etc/portage/package.* but not in {R,P}DEPEND.
Inconsistently, =foo/bar-*9 is not accepted in /etc/portage/package.* either

This behaviour his highly inconsistent and confusing, and I would really have to experiment to understand whether the above */*-*9999* would match the version 99991 and what */*-*alp* would match.

I suggest to implement PMS-compliant behaviour concerning versions throughout.
The particular special case in the manpage could be replaced by
=*/*-9999*
=*/*-99999999*
which is better anyway since it will not match 19999 or 1.9999
Comment 1 Martin Väth 2016-02-06 12:41:39 UTC
Since there is no reaction to this bug, I reintroduced in eix-0.31.7 an "extended version globbing" which seems to match current portage's behaviour.

I guess that I can close this as WONTFIX.