On Fri, 20 May 2005 22:49:50 +0100 Tom Wesley <tom@tomaw.org> wrote:
| On Fri, 2005-05-20 at 22:22 +0100, Ciaran McCreesh wrote:
| > Not gonna happen. Emulators don't cut it and won't find all the
| > problems (but they will find a load of other bogus non-issues).
| > Plus, from experience I'd say that at least half our devs wouldn't
| > have a clue where to start when doing arch testing...
| 
| Add this HOWTO arch test to your developer docs.  Very nice by the
| way.

Could do. I intend to include sections for domain-specific and
task-specific tasks at some point. The Debian Policy Manual does this to
a certain extent -- they have sections on things like "what to do if
your app needs to install cron jobs", "what to do if your app installs
shared libraries", "Emacs lisp programs" and various others. I'm kinda
tinkering with the best way for us to do a similar thing. There've been
a few requests for an "X11 Apps" section in The Doc, for example.

I guess arch-specific commentary would be good too. Would anyone from
any of the arch teams that I don't work on be prepared to feed me with
information?

Of course, a lot of arch testing is still down to experience. As with
everything else, docs can help as a reference but they can't replace
skilled devs, nor can they replace having an arch team that actually
discusses things and coordinates keywording.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm