pacman/pactest/tests/ldconfig001.py

# quick note here - chroot() is expected to fail.  We're not checking the
# validity of the scripts, only that they fire (or try to)
self.description = "Make sure ldconfig runs on an add operation"

p = pmpkg("dummy")
self.addpkg(p)

# --debug is necessary to check PACMAN_OUTPUT
self.args = "--debug -U %s" % p.filename()

self.addrule("PACMAN_RETCODE=0")
self.addrule("PACMAN_OUTPUT=ldconfig")
ldconfig changes from CVS forward-porting some 3.0.2 changes * Nagy's ldconfig fix * 3 new pactests to check if ldconfig runs Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com> 2007-04-16 20:34:57 -05:00			`# quick note here - chroot() is expected to fail. We're not checking the`
			`# validity of the scripts, only that they fire (or try to)`
			`self.description = "Make sure ldconfig runs on an add operation"`

			`p = pmpkg("dummy")`
			`self.addpkg(p)`

			`# --debug is necessary to check PACMAN_OUTPUT`
Move -A pactests that are relevant to -U, clean the rest out This is in anticipation of removing the -A/--add option from the pacman frontend. I've went through each of the pacman pactests that used the -A operation and decided whether they were worth keeping, whether there was already an upgrade test doing the same thing, or whether it should be moved over. The GIT rename log should make several of the moves obvious, but for those that were deleted: add001: handled by upgrade004 add002: worthless add004: worthless add010: handled by upgrade011 add050: handled by upgrade010 Signed-off-by: Dan McGee <dan@archlinux.org> 2008-03-08 14:04:06 -06:00			`self.args = "--debug -U %s" % p.filename()`
ldconfig changes from CVS forward-porting some 3.0.2 changes * Nagy's ldconfig fix * 3 new pactests to check if ldconfig runs Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com> 2007-04-16 20:34:57 -05:00
			`self.addrule("PACMAN_RETCODE=0")`
			`self.addrule("PACMAN_OUTPUT=ldconfig")`