| 1 |
On Fri, 20 May 2005 22:49:50 +0100 Tom Wesley <tom@×××××.org> wrote: |
| 2 |
| On Fri, 2005-05-20 at 22:22 +0100, Ciaran McCreesh wrote: |
| 3 |
| > Not gonna happen. Emulators don't cut it and won't find all the |
| 4 |
| > problems (but they will find a load of other bogus non-issues). |
| 5 |
| > Plus, from experience I'd say that at least half our devs wouldn't |
| 6 |
| > have a clue where to start when doing arch testing... |
| 7 |
| |
| 8 |
| Add this HOWTO arch test to your developer docs. Very nice by the |
| 9 |
| way. |
| 10 |
|
| 11 |
Could do. I intend to include sections for domain-specific and |
| 12 |
task-specific tasks at some point. The Debian Policy Manual does this to |
| 13 |
a certain extent -- they have sections on things like "what to do if |
| 14 |
your app needs to install cron jobs", "what to do if your app installs |
| 15 |
shared libraries", "Emacs lisp programs" and various others. I'm kinda |
| 16 |
tinkering with the best way for us to do a similar thing. There've been |
| 17 |
a few requests for an "X11 Apps" section in The Doc, for example. |
| 18 |
|
| 19 |
I guess arch-specific commentary would be good too. Would anyone from |
| 20 |
any of the arch teams that I don't work on be prepared to feed me with |
| 21 |
information? |
| 22 |
|
| 23 |
Of course, a lot of arch testing is still down to experience. As with |
| 24 |
everything else, docs can help as a reference but they can't replace |
| 25 |
skilled devs, nor can they replace having an arch team that actually |
| 26 |
discusses things and coordinates keywording. |
| 27 |
|
| 28 |
-- |
| 29 |
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) |
| 30 |
Mail : ciaranm at gentoo.org |
| 31 |
Web : http://dev.gentoo.org/~ciaranm |
Archives