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.50) id 1EbJMm-0004oS-1P for garchives@archives.gentoo.org; Sun, 13 Nov 2005 15:02:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jADF1CwH027538; Sun, 13 Nov 2005 15:01:12 GMT Received: from mail.twi-31o2.org (66-191-187-123.dhcp.gnvl.sc.charter.com [66.191.187.123]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jADExKZn030491 for ; Sun, 13 Nov 2005 14:59:20 GMT Received: from localhost (localhost [127.0.0.1]) by mail.twi-31o2.org (Postfix) with ESMTP id E2B0124801F for ; Sun, 13 Nov 2005 09:49:48 -0500 (EST) Received: from mail.twi-31o2.org ([127.0.0.1]) by localhost (gravity.twi-31o2.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01269-04 for ; Sun, 13 Nov 2005 09:49:44 -0500 (EST) Received: from vertigo.twi-31o2.org (vertigo.twi-31o2.org [192.168.0.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.twi-31o2.org (Postfix) with ESMTP id 3468524801E for ; Sun, 13 Nov 2005 09:49:44 -0500 (EST) Subject: Re: [gentoo-dev] Re: Re: GLEP 42 "Critical News Reporting" Round Two From: Chris Gianelloni To: gentoo-dev@lists.gentoo.org In-Reply-To: <200511130105.48799.jstubbs@gentoo.org> References: <436CAC58.4090809@gentoo.org> <200511121339.05413.jstubbs@gentoo.org> <1131809671.8774.19.camel@vertigo.twi-31o2.org> <200511130105.48799.jstubbs@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Tzs2syjlopjeWBcNL1JY" Organization: Gentoo Linux Date: Sun, 13 Nov 2005 09:55:25 -0500 Message-Id: <1131893725.8774.31.camel@vertigo.twi-31o2.org> 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 X-Mailer: Evolution 2.4.1 X-Virus-Scanned: amavisd-new at twi-31o2.org X-Archives-Salt: 525efde9-6e2e-4ca1-b973-d6c96aa34f41 X-Archives-Hash: 31f904b3829b0d3b96c8e9b7a6bd73f4 --=-Tzs2syjlopjeWBcNL1JY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-11-13 at 01:05 +0900, Jason Stubbs wrote: > > It is my opinion that the news reading application need not be > > integrated into portage. As far as I have understood it, the only real > > thing that anyone has required portage itself to do is to > > *automatically* spit out "You have $n unread news messages. Please use > > $bleh to read them" at certain times (after sync, after --pretend, > > before/after a merge). I don't see this as being something very > > complex. I would assume that some extra code would need to be written > > into the sync code somewhere to sort the messages. >=20 > This, I get. What I'm wondering about is the `emerge --news` that is refe= rred=20 > to every so often. emerge --news is just what people have been calling the news reader. As far as I can see, unless you *want* portage to handle the news reading, it should *not* have a --news option. > To be honest, this is the part that I don't like the most. Integrating co= de=20 > into portage to copy files here and there based on some predefined rules = and=20 > news readers reading and renaming files based on some predefined rules... > A filesystem based API just doesn't seem very robust to change. >=20 > I'd prefer that either the post-sync handling code is not integrated into= =20 > portage and portage just triggers some external script - or - portage exp= oses=20 > an API (via python and bash) for accessing and updating news items. I'd=20 > prefer the latter but I get the impression that most prefer the former. I believe that we have been under the impression that you guys preferred to keep this out of portage as much as possible. I think an API built into portage *would* be the best method for this. --=20 Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux --=-Tzs2syjlopjeWBcNL1JY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDd1PdkT4lNIS36YERAphNAJwL/EBGzI4iZBFrAgI3gesPlQK8zwCgrER0 /fOPM27OFOLFhf9Sdid1PfA= =p1m0 -----END PGP SIGNATURE----- --=-Tzs2syjlopjeWBcNL1JY-- -- gentoo-dev@gentoo.org mailing list