public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keywording, for the umpteenth time
Date: Fri, 20 May 2005 23:38:56 +0100	[thread overview]
Message-ID: <20050520233856.5ef8f45d@snowdrop> (raw)
In-Reply-To: <1116625790.9174.5.camel@tom.tomaw.org>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

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


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-05-20 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 16:42 [gentoo-dev] Keywording, for the umpteenth time Jason Wever
2005-05-20 18:53 ` Duncan Coutts
2005-05-20 19:42   ` Mike Frysinger
2005-05-20 20:09   ` Jason Wever
2005-05-20 20:51     ` Brian Jackson
2005-05-20 21:18       ` Michael Cummings
2005-05-21  0:17         ` Donnie Berkholz
2005-05-20 21:22       ` Ciaran McCreesh
2005-05-20 21:49         ` Tom Wesley
2005-05-20 22:38           ` Ciaran McCreesh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050520233856.5ef8f45d@snowdrop \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox