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.54) id 1Em0FJ-0003pP-9P for garchives@archives.gentoo.org; Tue, 13 Dec 2005 02:50:29 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBD2nCZ2012679; Tue, 13 Dec 2005 02:49:12 GMT Received: from mta1.adelphia.net (mta1.adelphia.net [68.168.78.175]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBD2lBqr009563 for ; Tue, 13 Dec 2005 02:47:11 GMT Received: from [192.168.0.165] (really [68.168.137.100]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051213024512.IOXG22124.mta10.adelphia.net@[192.168.0.165]> for ; Mon, 12 Dec 2005 21:45:12 -0500 Message-ID: <439E35B2.5050801@leetworks.com> Date: Mon, 12 Dec 2005 21:45:06 -0500 From: Andrew Muraco User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051102) X-Accept-Language: en-us, en 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: GLEP 42 (Critical news reporting) updates References: <20051211013550.66bfd7d2@snowdrop.home> <200512131117.30933.jstubbs@gentoo.org> <20051213022200.05b9f6a6@snowdrop.home> <200512131139.14099.jstubbs@gentoo.org> In-Reply-To: <200512131139.14099.jstubbs@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 149b278a-0b09-4da5-9bd4-e12ce828284b X-Archives-Hash: 1f6cfbc67ccfbc9bccdfe723d7ee6d3e Jason Stubbs wrote: >On Tuesday 13 December 2005 11:22, Ciaran McCreesh wrote: > > >>On Tue, 13 Dec 2005 11:17:30 +0900 Jason Stubbs >> >>wrote: >>| So what are you going to do? I asked already but you didn't answer. >>| How are you going to find $PORTDIR/metadata/news? >> >>At present, by using portageq with a hardcoded suffix. If in the future >>Portage introduces new functionality, then clients and the >>specification can easily be updated to handle said functionality. >> >> > >And how can that be adapted to work with overlays, completely ignoring the >possibility of distinct repositories. Overlays is something that exists >already and news support for them is a request that will appear as soon as >news support is added. > >-- >Jason Stubbs > > Your Point is Moot because an overlay (at present) is going to be exprimental software, (unsupported offically anyways) and so you _should_ know what risks your taking, this GLEP is to warn you about supported updates/changes which you _need_ to know about. Why should an overlay need to have news if the user has the consciensely update and maintain it to begin it. -- gentoo-dev@gentoo.org mailing list