public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: hwoarang@gentoo.org
Cc: klausman@gentoo.org,vapier@gentoo.org,gmsoft@gentoo.org,armin76@gentoo.org,mattst88@gentoo.org,ago@gentoo.org,jdhore@gentoo.org,jer@gentoo.org,
	gentoo-dev@lists.gentoo.org,council@gentoo.org
Subject: [Bug 304435] Developer Handbook should document how/when to touch arch profiles' files (was: Re: [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc)
Date: Sat, 2 Nov 2013 22:22:37 +0100	[thread overview]
Message-ID: <20131102222237.131a6827@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52657D71.4080009@gentoo.org>

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

On Mon, 21 Oct 2013 20:16:01 +0100
Markos Chandras <hwoarang@gentoo.org> wrote:

> Lets calm down a little bit. Our documentation is nowhere near perfect
> and common sense is not always obvious (we have hundreds of people
> claiming that the opposite). Instead of arguing in public how about we
> contribute some patches in devmanual to avoid similar problems in the
> future?

Hello, that indeed should be the way to go; but I came across something
relevant to this, as I was searching for an unrelated devmanual bug.

It seems like we do should discuss this in public:

    https://bugs.gentoo.org/show_bug.cgi?id=304435#c33 (Comment 33)

Looking a bit back up, it seems I've got a blanket to touch them:

    https://bugs.gentoo.org/show_bug.cgi?id=304435#c23 (Comment 23)

And that's also probably why a lot of other people have done so.

Though I agree with Jeroen Roovers as to why not to, because it results
in more work (as more files are touched) and there are some arches that
simply don't want it. So, I think we should proceed with discussing
this amongst the architectures and perhaps council and then proceed on
getting it into the devmanual so that we can act consistently.

Therefore I suggest that the arch teams and/or the council clarify when
developers can touch which files in the architecture sub directories of
profiles/.

I do want to help by writing up a patch, but I'd like to see consensus
first to avoid documenting something that not every arch team follows.

I'd suggest we discuss and/or vote on Jeroen Roovers' opinion:

    http://article.gmane.org/gmane.linux.gentoo.devel/88609

Prior discussion that lead to this:

    http://thread.gmane.org/gmane.linux.gentoo.devel/88562 (frames)
    http://www.gossamer-threads.com/lists/gentoo/dev/279926 (plain)

The bug that has lead to the prior discussion:

    https://bugs.gentoo.org/show_bug.cgi?id=488318

Prior discussion with Jeroen Roovers' opinion that was not answered to:

    http://gentoo.2317880.n4.nabble.com/best-way-to-use-profiles-and-package-use-mask-td16465.html

Please note that I do not intend a negative connotation with the word;
I agree with it, as it seems like common sense to me. But I just label
it opinion because I am unsure if this is collaborative knowledge [or
common sense] among archictecture teams; in any case, for outstanders
this is undocumented which can lead to moments of misunderstanding.

Thank you very much in advance.

CC-ed: Arch leads, frequent arch member, related persons, council.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-11-02 21:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-488318-23709@http.bugs.gentoo.org/>
     [not found] ` <bug-488318-23709-Ghdn7p7FCs@http.bugs.gentoo.org/>
2013-10-19 17:01   ` [gentoo-dev] Re: [Bug 488318] media-video/mpv[luajit] - Keyword request on alpha, arm, ppc, ppc64, sparc Jeroen Roovers
2013-10-19 17:43     ` Tom Wijsman
2013-10-20 10:18       ` Markos Chandras
2013-10-20 10:40         ` Patrick Lauer
2013-10-20 11:41           ` Markos Chandras
2013-10-20 12:30             ` Tom Wijsman
2013-10-21 13:50               ` Jeroen Roovers
2013-10-21 15:32                 ` Tom Wijsman
2013-10-21 16:31                   ` Jeroen Roovers
2013-10-21 17:03                     ` Tom Wijsman
2013-10-20 14:05             ` Patrick Lauer
2013-10-21 13:32             ` Jeroen Roovers
2013-10-21 16:19               ` Tom Wijsman
2013-10-21 19:16               ` Markos Chandras
2013-11-02 21:22                 ` Tom Wijsman [this message]
2013-10-20 12:23         ` Tom Wijsman

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=20131102222237.131a6827@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=ago@gentoo.org \
    --cc=armin76@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gmsoft@gentoo.org \
    --cc=hwoarang@gentoo.org \
    --cc=jdhore@gentoo.org \
    --cc=jer@gentoo.org \
    --cc=klausman@gentoo.org \
    --cc=mattst88@gentoo.org \
    --cc=vapier@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