From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HknkK-0006vU-NT for garchives@archives.gentoo.org; Sun, 06 May 2007 20:54:21 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l46Kr3wJ032176; Sun, 6 May 2007 20:53:03 GMT Received: from dd14500.kasserver.com (dd14500.kasserver.com [85.13.135.241]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l46Kp0ml029806 for ; Sun, 6 May 2007 20:51:00 GMT Received: from hoshino (unknown [82.139.196.236]) by dd14500.kasserver.com (Postfix) with ESMTP id 4214814304 for ; Sun, 6 May 2007 22:50:59 +0200 (CEST) From: expose@luftgetrock.net To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 42 news item for review: Radiant upgrade Date: Sun, 6 May 2007 22:50:40 +0200 User-Agent: KMail/1.9.5 References: <1178433936.13701.10.camel@ip6-localhost> <463E3BB3.4010105@gentoo.org> <20070506213816.49d44d37@snowflake> In-Reply-To: <20070506213816.49d44d37@snowflake> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705062250.40828.expose@luftgetrock.net> X-Archives-Salt: 8614d1bf-6b13-4131-9d61-f3cdd1d4b3be X-Archives-Hash: 4b623888e51a14192a6bf2d4479e783a Am Sonntag 06 Mai 2007 22:38 schrieb Ciaran McCreesh: > On Sun, 06 May 2007 22:33:55 +0200 > > Jakub Moc wrote: > > Ciaran McCreesh napsal(a): > > > On Sun, 6 May 2007 16:00:56 -0400 > > > > > > Dan Meltzer wrote: > > >>> Er, making elog logged by default would not solve the "requires an > > >>> explicit read" problem. Making elog require an explicit read would > > >>> be far too annoying because most elog notices are noise. We've > > >>> been over this already. > > >> > > >> Not if one filters it properly. ELOG_CLASSES="warn error" sounds > > >> like a sane default to me. > > > > > > So you want users to have to explicitly acknowledge all ewarn > > > notices? Now *that*'s a way of making the system useless by > > > overusing it. > > > > Why would you acknowledge them? They are a different feature (plus, > > seriously no mail gets automagically marked as read, if you use the > > mail elog feature e.g. Maybe you should actually try to use the stuff > > before recycling your 'our experience shows' and 'elog sucks' > > scratched record once again.) > > Maybe you should reread the context I've quoted. Dan is proposing > making elog require explicit acknowledgements. > > > Plus, why's this thread been hijacked again for the paludis upgrade > > stuff that doesn't need any news at all and that's been committed in > > breach of GLEP42 itself?! > > Because some people won't stop looking for any available excuse to rant > about anything that has or can be made to have 'paludis' in it, and > they don't bother to read the rest of the discussion before they do so. Talking about yourself again? > > - drop this "users like it" and "experience has shown" stuff. > > Experience based on 4 news items is no experience at all; experience > > based on one-package overlay is irrelevant wrt a repository with > > thousands of ebuilds; and "users like it" may be nice for one package > > overlay, and a genuine PITA for a tree with thousands of ebuilds at > > the same time. Repeating it doesn't go anywhere, nor will it make any > > of your point more valid. > > And yet it's infinitely more experience than anyone else has at this > point. When there's a better collection of data available we'll use > that instead. It might be infinitely more, yet it still isnt worth anything for the reasons already explained which you, I guess, have accidently overlooked again. I bet your users wont like reading zillions of - for gods sake - very very trivial news items for each and every package that hits the tree or they upgrade or what so ever else. And if your expierence shows they will do like this, just write all the news items, and put them up your own repository, at let your happy users read them from there. -- gentoo-dev@gentoo.org mailing list