public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 09-10-2012
Date: Sat, 29 Sep 2012 17:10:06 +0100	[thread overview]
Message-ID: <20120929171006.7ba6d775@googlemail.com> (raw)
In-Reply-To: <20583.7211.128410.806714@a1i15.kph.uni-mainz.de>

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

On Sat, 29 Sep 2012 18:04:59 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Sat, 29 Sep 2012, Ciaran McCreesh wrote:
> >>     d) Require a) for Package managers and b) by tree policy
> >>        (Postel's Law, brought up by mgorny). Practically, this
> >>        would mean that repoman would reject "foo-1" as package
> >>        name, but the rest of Portage would accept it.
> 
> > Postel's Law is what lead to the current state of HTML and
> > JavaScript, where everything has to be tested carefully on dozens of
> > different browser versions and littered with workarounds. Accepting
> > lax input just leads to lax input being provided...
> 
> Providing lax input is not at all Postel's Law, but the opposite of
> it.

But as you can see from HTML, and all the stuff Portage accepts
currently, and from countless other examples, the only way to prevent
bad input from being provided is to reject it. Following one half of
Postel's law just leads to the other half being violated.

> In our case, strict input would be enforced with repoman.

Repoman can't parse bash code.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2012-09-29 18:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  9:24 [gentoo-project] Call for agenda items -- Council meeting 09-10-2012 Fabian Groffen
2012-09-25  9:59 ` Ulrich Mueller
2012-09-27  6:19   ` Ulrich Mueller
2012-09-27 22:13     ` Brian Harring
2012-09-28  0:14       ` Ulrich Mueller
2012-09-28 12:12         ` Brian Harring
2012-10-03  5:04       ` Donnie Berkholz
2012-10-03  6:44         ` Ulrich Mueller
2012-10-03  6:56           ` Matt Turner
2012-10-03  8:31             ` Ulrich Mueller
2012-09-29 15:51     ` Ciaran McCreesh
2012-09-29 16:04       ` Ulrich Mueller
2012-09-29 16:10         ` Ciaran McCreesh [this message]
2012-09-25 19:32 ` Pacho Ramos
2012-10-02 11:30   ` Fabian Groffen
2012-10-03 17:18     ` Pacho Ramos
2012-10-04 18:32       ` Pacho Ramos
2012-10-05  6:28         ` Fabian Groffen
2012-10-05  6:41           ` Pacho Ramos
2012-10-05  6:43           ` Patrick Lauer
2012-10-05  8:46             ` Ulrich Mueller
2012-10-05 10:31               ` Rich Freeman
2012-10-05 14:51                 ` Jeff Horelick
2012-10-05 17:35                 ` Pacho Ramos

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=20120929171006.7ba6d775@googlemail.com \
    --to=ciaran.mccreesh@googlemail.com \
    --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