mirror of
https://github.com/moparisthebest/pacman
synced 2024-10-31 15:45:03 -04:00
Add two new pactests for --dbonly
It caught me by surprise that: 1. These weren't being tested at all 2. The --dbonly combined with -U not only "works" but is also completely undocumented. It also has some weird behavior on install vs. upgrade that may need addressing. Add some tests which will hopefully provoke some discussion. Signed-off-by: Dan McGee <dan@archlinux.org>
This commit is contained in:
parent
f9fa822ccb
commit
9528c36452
17
pactest/tests/database010.py
Normal file
17
pactest/tests/database010.py
Normal file
@ -0,0 +1,17 @@
|
||||
# TODO: these are labeled as database packages because they sure seem to me to
|
||||
# be database-type operations. In their current implementation however they are
|
||||
# calling -U and -R rather than -D. Obviously the tests will need to be updated
|
||||
# if this changes.
|
||||
self.description = "Remove a package with --dbonly, no files touched"
|
||||
|
||||
p = pmpkg("dummy")
|
||||
p.files = ["bin/dummy",
|
||||
"usr/man/man1/dummy.1"]
|
||||
self.addpkg2db("local", p)
|
||||
|
||||
self.args = "-R --dbonly %s" % p.name
|
||||
|
||||
self.addrule("PACMAN_RETCODE=0")
|
||||
self.addrule("!PKG_EXIST=dummy")
|
||||
for f in p.files:
|
||||
self.addrule("FILE_EXIST=%s" % f)
|
17
pactest/tests/database011.py
Normal file
17
pactest/tests/database011.py
Normal file
@ -0,0 +1,17 @@
|
||||
# TODO: these are labeled as database packages because they sure seem to me to
|
||||
# be database-type operations. In their current implementation however they are
|
||||
# calling -U and -R rather than -D. Obviously the tests will need to be updated
|
||||
# if this changes.
|
||||
self.description = "Install a package with --dbonly, no files touched"
|
||||
|
||||
p = pmpkg("dummy")
|
||||
p.files = ["bin/dummy",
|
||||
"usr/man/man1/dummy.1"]
|
||||
self.addpkg(p)
|
||||
|
||||
self.args = "-U --dbonly %s" % p.filename()
|
||||
|
||||
self.addrule("PACMAN_RETCODE=0")
|
||||
self.addrule("PKG_EXIST=dummy")
|
||||
for f in p.files:
|
||||
self.addrule("!FILE_EXIST=%s" % f)
|
31
pactest/tests/database012.py
Normal file
31
pactest/tests/database012.py
Normal file
@ -0,0 +1,31 @@
|
||||
# TODO: these are labeled as database packages because they sure seem to me to
|
||||
# be database-type operations. In their current implementation however they are
|
||||
# calling -U and -R rather than -D. Obviously the tests will need to be updated
|
||||
# if this changes.
|
||||
self.description = "Upgrade a package with --dbonly, no files touched"
|
||||
|
||||
lp = pmpkg("dummy")
|
||||
lp.files = ["bin/dummy",
|
||||
"usr/man/man1/dummy.1"]
|
||||
self.addpkg2db("local", lp)
|
||||
|
||||
p = pmpkg("dummy", "2.0-1")
|
||||
p.files = ["bin/dummy",
|
||||
"bin/dummy2",
|
||||
"usr/man/man1/dummy.1"]
|
||||
self.addpkg(p)
|
||||
|
||||
self.args = "-U --dbonly %s" % p.filename()
|
||||
|
||||
self.addrule("PACMAN_RETCODE=0")
|
||||
self.addrule("PKG_EXIST=dummy")
|
||||
self.addrule("PKG_VERSION=dummy|2.0-1")
|
||||
for f in lp.files:
|
||||
self.addrule("!FILE_EXIST=%s" % f)
|
||||
# TODO: I honestly think the above should NOT delete the original files, it
|
||||
# should upgrade the DB entry without touching anything on the file system.
|
||||
# E.g. this test should be the same as:
|
||||
# pacman -R --dbonly dummy && pacman -U --dbonly dummy.pkg.tar.gz
|
||||
#for f in lp.files:
|
||||
# self.addrule("FILE_EXIST=%s" % f)
|
||||
self.addrule("!FILE_EXIST=bin/dummy2")
|
Loading…
Reference in New Issue
Block a user