diff options
author | Dominik Fischer <d.f.fischer@web.de> | 2015-12-07 21:37:09 +0100 |
---|---|---|
committer | Allan McRae <allan@archlinux.org> | 2016-01-15 14:47:36 +1000 |
commit | 9813107c3368684784706cf2b77bd056bea58e3c (patch) | |
tree | 037c64627ef58151e82202de1a5c682764d2323e /contrib/bacman.sh.in | |
parent | 00c03295315cb2d359733858d2945bb6a7070c70 (diff) | |
download | pacman-9813107c3368684784706cf2b77bd056bea58e3c.tar.xz |
test version range restrictions corner case
The test introduced herein illustrates a behavior that may be unexpected
to package writers.
It creates a package "pkg3" that is configured to depend on a
"dependency" which version is between 3 and 4, inclusive. Two other
packages are already present, providing "dependency" in version 2 and 5,
respectively. So, the situation looks roughly like this:
pkg1 pkg3 pkg2
provides depends on provides
| <------------> |
version __________2____________3____________4____________5___________...
This seems to be enough to satisfy pacman when installing "pkg3". From
an iterative standpoint, this is completely logical: First, the
requirement "dependency>=3" is checked. There is a package that
satisfies this restriction, it is called "pkg2". Afterwards,
"dependency<=4" is covered in the same way by "pkg1".
Nonetheless, what a package writer intends when specifying
depends=('dependency>=3' 'dependency<=4')
is most probably that pacman should only allow this package to be
installed when there indeed is a package present that provides a version
of "dependency" that lies _between_ 3 and 5.
Signed-off-by: Dominik Fischer <d dot f dot fischer at web dot de>
Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'contrib/bacman.sh.in')
0 files changed, 0 insertions, 0 deletions