On Tue, Aug 06, 2013 at 08:32:37AM +0200, Marcus Meissner wrote:
On Tue, Aug 06, 2013 at 08:14:11AM +0200, Bernhard Voelker wrote:
On 08/05/2013 04:37 PM, Bernhard Voelker wrote:
On 08/05/2013 03:48 PM, Philipp Thomas wrote:
Why? We have the testsuite package that nearly nobody will want to install, so why shoudn't we have a package which a test user?
[...]
What I wanted is groupadd abuild2 usermod -a -G abuild2 abuild right before "make check-very-expensive" in the %check section.
Hmm, with both above sentences close to each other, I have the following idea: can I add the user to such a second group in the e.g. %post section of coreutils-testsuite, and then BuildReq:coreutils-testsuite to have that test environment in the following run? (Sounds like a little cycle, but maybe ...?)
You can probably do it a bit different.
coreutils-testsuite.spec, create a user in %post
and then run the testsuite in %check as %check is run after the package is installed into the system.
This would avoid loops.
What about to create coreutils-testsuite-setup package with following %post groupadd abuild2 usermod -a -G abuild2 abuild and with README.SUSE explaining the reason for it, becasue empty packages are not allowed in SUSE. Then add BuildRequires: coreutils-testsuite-setup to coreutils(-testsuite).spec and run make check. As groupadd/usermod are in shadow package, this won't even make any build cycles. Regards Michal Vyskocil
Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org