public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2013-05-14
Date: Sat, 27 Apr 2013 23:27:43 +0200	[thread overview]
Message-ID: <20130427232743.16c3a89e@gentoo.org> (raw)
In-Reply-To: <517C03E8.7040406@gentoo.org>

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

On Sat, 27 Apr 2013 19:59:20 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:

> Please respond to this email with agenda items. Please do not hesitate
> to repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).

I would like to request the Council to vote on the topic of changing
the ${D} and ${ROOT} variables not to be terminated with a trailing
slash. To decrease confusion and improve forward compatibility, this
would benefit from retroactively removing the 'must end with a trailing
slash' guarantees from PMS, changing it to undefined and working on
fixing the ebuilds which relied on those.

Then, in a future EAPI a common guarantee will be added that all path
variables do not end with a trailing slash.

The topic has been brought on the ml [1] and there was some discussion
in the relevant bug [2] as well. I've written a simple plan on how to
handle it effectively [3], attached a PMS patch and two dedicated QA
checks for repoman.

The idea has met mostly positive feedback. Ciaran is opposed to it.
The number of ebuilds needing changing for the 'no trailing slash'
standard is estimated to be at least 30 times smaller than those which
incorrectly assume no trailing slash in ${D} -- which proves that
the current rule is unknown to most of the developers.

[1]:http://thread.gmane.org/gmane.linux.gentoo.devel/84989
[2]:https://bugs.gentoo.org/show_bug.cgi?id=465772
[3]:https://bugs.gentoo.org/show_bug.cgi?id=465772#c20

-- 
Best regards,
Michał Górny

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

  reply	other threads:[~2013-04-27 21:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27 16:59 [gentoo-project] Call for agenda items - Council meeting 2013-05-14 Petteri Räty
2013-04-27 21:27 ` Michał Górny [this message]
2013-05-01  7:37 ` Ulrich Mueller
2013-05-01 15:15 ` Mike Gilbert
2013-05-01 15:18 ` Zac Medico
2013-05-01 15:22   ` Ciaran McCreesh
2013-05-01 15:28     ` Michał Górny
2013-05-01 15:35       ` Ciaran McCreesh
2013-05-01 17:27         ` Zac Medico
2013-05-01 17:30           ` Ciaran McCreesh
2013-05-01 17:35             ` Rich Freeman
2013-05-01 17:45               ` Ciaran McCreesh
2013-05-01 16:35     ` Rich Freeman
2013-05-01 15:39 ` Michał Górny

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=20130427232743.16c3a89e@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@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