public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SRC_URI component naming collision
Date: Sun, 26 Feb 2006 22:25:19 -0500	[thread overview]
Message-ID: <4402711F.9090702@gentoo.org> (raw)
In-Reply-To: <1141008794.22804.27.camel@Sabin.anyarch.net>

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

Daniel Ostrow wrote:
> On Sun, 2006-02-26 at 22:17 +0000, Stuart Herbert wrote:
> 
>>On Sun, 2006-02-26 at 17:02 -0500, Daniel Ostrow wrote:
>>
>>>That would work for fetch restricted packages, not nomirrored ones.
>>>
>>>--Dan
>>
>>/me nods.  That's what we'll have to do.  Unfortunately, it leaves users
>>with a worse experience than before, but until I can find a way to reach
>>the QA team and help them see my pov as the package maintainer, what
>>else can I do? :(

It's only 'worse' than before if you assume that all your users read the
documentation, otherwise they end up futzing around with their distfiles
trying to figure out why the checksum is incorrect.  This way the ebuild
will die right off and the information is presented at the same time.
They can go get the ebuild and rename it ( hell you can even provide
them with the wget command to do so ).  As such, glad this is resolved
with at least some agreement on all sides :)

--Alec Warner

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 894 bytes --]

  reply	other threads:[~2006-02-27  3:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 14:19 [gentoo-dev] SRC_URI component naming collision Ciaran McCreesh
2006-02-24 22:51 ` Jochen Maes
2006-02-24 23:09 ` Doug Goldstein
2006-02-25 15:24 ` Paul de Vrieze
2006-02-25 21:29   ` Drake Wyrm
2006-02-26 14:53     ` Paul de Vrieze
2006-02-26 19:45 ` Stuart Herbert
2006-02-26 19:56   ` Mike Frysinger
2006-02-26 20:30     ` Stuart Herbert
2006-02-26 20:00   ` Ciaran McCreesh
2006-02-26 20:46     ` Stuart Herbert
2006-02-26 21:04       ` Ciaran McCreesh
2006-02-26 21:30         ` Stuart Herbert
2006-02-26 21:40           ` Ciaran McCreesh
2006-02-26 22:13             ` Stuart Herbert
2006-02-26 22:31               ` Ciaran McCreesh
2006-02-27 10:02             ` Paul de Vrieze
2006-02-27 16:33               ` Ciaran McCreesh
2006-02-27 16:46                 ` Lance Albertson
2006-02-27 17:11                   ` Ciaran McCreesh
2006-02-26 20:02   ` Daniel Ostrow
2006-02-26 21:29 ` Robin H. Johnson
2006-02-26 21:54   ` Stuart Herbert
2006-02-26 22:02     ` Daniel Ostrow
2006-02-26 22:17       ` Stuart Herbert
2006-02-26 22:27         ` Ciaran McCreesh
2006-02-27  2:53         ` Daniel Ostrow
2006-02-27  3:25           ` Alec Warner [this message]
2006-02-27 10:05   ` Paul de Vrieze
2006-02-27 16:34     ` Ciaran McCreesh
2006-02-27 20:23       ` Robin H. Johnson
2006-02-28 14:16     ` Marius Mauch
2006-02-28 15:28       ` Paul de Vrieze

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=4402711F.9090702@gentoo.org \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@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