From: Richard Purdie <rpurdie@rpsys.net>
To: Using the OpenEmbedded metadata to build Linux Distributions
<openembedded-devel@openembedded.org>
Subject: Re: [RFC] Removing MAINTAINER field from recipes
Date: Mon, 09 Oct 2006 09:58:01 +0100 [thread overview]
Message-ID: <1160384282.5741.22.camel@localhost.localdomain> (raw)
In-Reply-To: <74d0deb30610090140g40716743k35a2cddb555018d4@mail.gmail.com>
On Mon, 2006-10-09 at 10:40 +0200, pHilipp Zabel wrote:
> On 10/9/06, Richard Purdie <rpurdie@rpsys.net> wrote:
> > MAINTAINER would still exists but would become a distro variable so
> > distros would still use it to set the maintainer of distributed packages
> > but since this is usually a distro contact, setting it in a distro.conf
> > file shouldn't be a problem (and it can be overridden on a per package
> > basis MAINTAINER_pn-linux-opnzaurus = "").
>
> Does this mean we'll have additional per-distro .conf files
> which contain hundreds of MAINTAINER_pn-foo variables?
That is something for a distro to decide. In most cases, I see a distro
wanting a single point of contact so whilst it would be possible, I
don't see it happening. All current distros try and setup a single point
of contact as far as I know.
Richard
next prev parent reply other threads:[~2006-10-09 9:04 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 [this message]
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
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=1160384282.5741.22.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox