All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Graeme Gregory <dp@xora.org.uk>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] Removing MAINTAINER field from recipes
Date: Tue, 10 Oct 2006 19:08:14 +0300	[thread overview]
Message-ID: <1646477210.20061010190814@gmail.com> (raw)
In-Reply-To: <20061010153918.GD2541@stygia.hyboria>

Hello Graeme,

Tuesday, October 10, 2006, 6:39:18 PM, you wrote:

> A suggestion as to a possible format for MAINTAINERS file.

> I tried to be machine parsable and human parsable.

> DEVELOPER {
> NAME="Koen Kooi"
> NICK="koen"
> EMAIL="Koen Kooi <koen@openembedded.org>
> MACHINE="h2200 ipaq-pxa270"
> DISTRO="angstrom.*"
> RECPIPES="gnome/.* gnumeric/.*"
> }

  Well, just a note: this seems just like *too much machine* parsable
;-). As far as got from idea of removing the var, intention of the
list to be machine parsable was simple things, like sorting it
in some order or rendering in HTML. Not being able to write
a script which, for any given package, will return a maintainer for
it. In other words, I understood that intention was that maintainer
list's contents were intended for human consumption, and only syntax
of it should be machine-readable.

  Because otherwise, MAINTAINER field could have stayed the way it
was.

  Please correct me if I'm wrong.


Marcin Juszkiewicz wrote:

> Person:     Koen Kooi
> Mail:       koen@openembedded.org
> Website:    http://dominion.kabel.utwente.nl/koen/cms
> Machines:   h2200, ipaq-pxa270, efika, ep93xx, netbook-pro
> Distros:    Angstrom
> Recipes:    OpenSync,, GNOME, GPE, Matchbox
> Recipes:    abiword, bootchart, dia, farsight, freeciv, fuse, galago, geda,
> Recipes:    gimp, gnumeric, (g)obby, imposter, inkscape
> Recipes:    telepathy, tilibs, xchat, xournal. 


> Cheers

> G


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2006-10-10 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-08 21:33 [RFC] Removing MAINTAINER field from recipes Koen Kooi
2006-10-09  8:14 ` Graeme Gregory
2006-10-09  8:21 ` Richard Purdie
2006-10-09  8:26   ` Graeme Gregory
2006-10-09 16:03     ` Koen Kooi
2006-10-10  7:55       ` Graeme Gregory
2006-10-09  8:40   ` pHilipp Zabel
2006-10-09  8:58     ` Richard Purdie
2006-10-10 15:34   ` Marcin Juszkiewicz
2006-10-13  0:28     ` Jamie Lenehan
2006-10-13 13:22       ` Marcin Juszkiewicz
2006-10-14  1:59         ` Jamie Lenehan
2006-10-10 15:39 ` Graeme Gregory
2006-10-10 16:08   ` Paul Sokolovsky [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=1646477210.20061010190814@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=dp@xora.org.uk \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.