[arch-projects] [dbscripts] [PATCH 1/2] Make tests much more portable and usable

Dan McGee dpmcgee at gmail.com
Mon Jul 25 14:55:57 EDT 2011

On Mon, Jul 25, 2011 at 1:48 PM, Pierre Schmitz <pierre at archlinux.de> wrote:
> On Tue, 28 Jun 2011 21:58:14 -0500, Dan McGee wrote:
>> Using 'sudo' in a test? Not on my machine, I don't care how secure it
>> should be, it is totally unnecessary, not to mention the annoyance of
>> password prompts, needing the chroot setups, etc. Instead, use makepkg
>> directly along with some very vanilla makepkg.conf config files to do
>> the work.  This makes for a more reproducable environment as far as
>> makepkg settings goes.
> I prefer using devtools here instead of duplicating tools. This is only
> a test suite and packages need to be built only once.
What tools are we duplicating?

If the tests aren't self contained, they don't get run. It took me an
hour or more to get these running, and that is straight up

I will *not* ever give a script sudo access on my machine. Ever. Nor
will most other people writing improvements to these tests and

> This way we also make sure we get the same packages as a packager would
> get.
The same as makepkg? I don't understand at all what you mean by this
and how using makepkg directly is not the same as a packager would get
(if it isn't, then devtools is busted, and we aren't attempting to
test devtools here).

> Also your approach would need gcc-multilib to be able to build 32bit
> packages.
Well for starters your test suite won't even run on x86 because of
this, and the fact that you try to build 64 bit packages. But more
importantly, where does gcc-multilib even come into play here? You
aren't even building a real package, and there is no source code!

> --
> Pierre Schmitz, https://users.archlinux.de/~pierre

More information about the arch-projects mailing list