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 1EmApj-0003FR-Km for garchives@archives.gentoo.org; Tue, 13 Dec 2005 14:08:48 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBDE7YxG003908; Tue, 13 Dec 2005 14:07:34 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBDE4vnw032104 for ; Tue, 13 Dec 2005 14:04:57 GMT Received: from jj039137.ppp.dion.ne.jp ([211.4.39.137] helo=opteron246.suzuki-stubbs.home) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1EmAm0-00006j-Qk for gentoo-dev@lists.gentoo.org; Tue, 13 Dec 2005 14:04:57 +0000 Received: by opteron246.suzuki-stubbs.home (Postfix, from userid 1000) id 2018E201A48; Tue, 13 Dec 2005 23:05:21 +0900 (JST) From: Jason Stubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: GLEP 42 (Critical news reporting) updates Date: Tue, 13 Dec 2005 23:05:20 +0900 User-Agent: KMail/1.9 References: <20051211013550.66bfd7d2@snowdrop.home> <200512131139.14099.jstubbs@gentoo.org> <439E35B2.5050801@leetworks.com> In-Reply-To: <439E35B2.5050801@leetworks.com> 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: <200512132305.20882.jstubbs@gentoo.org> X-Archives-Salt: 1553c158-f4b6-40ff-96c1-2015dae33faf X-Archives-Hash: fc4021705cbd12359ad2e6c29e988424 On Tuesday 13 December 2005 11:45, Andrew Muraco wrote: > 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. > > Your Point is Moot ... Interesting use of capitals. > because an overlay (at present) is going to be exprimental software, or a repository from a non-English speaking community Gentoo site... > (unsupported offically anyways) and so you _should_ know what risks your > taking, except if your a new non-English-speaking user utilizing such a repository. > this GLEP is to warn you about supported updates/changes which you _need_ to > know about. This GLEP is about getting news regarding a set of ebuilds to the user. Making it only about the Gentoo supported tree serves no purpose. > Why should an overlay need to have news if the user has the consciensely > update and maintain it to begin it. Because they already support package.mask, thirdpartymirrors, eclasses and just about anything else that exists in the supported tree. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list