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 1ElbL7-0006HU-VQ for garchives@archives.gentoo.org; Mon, 12 Dec 2005 00:14:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBC0E771025501; Mon, 12 Dec 2005 00:14:07 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 jBC0Baoe012794 for ; Mon, 12 Dec 2005 00:11:36 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 1ElbHz-0003sI-UF for gentoo-dev@lists.gentoo.org; Mon, 12 Dec 2005 00:11:36 +0000 Received: by opteron246.suzuki-stubbs.home (Postfix, from userid 1000) id 1C9F7201A48; Mon, 12 Dec 2005 09:11:54 +0900 (JST) From: Jason Stubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP 42 (Critical news reporting) updates Date: Mon, 12 Dec 2005 09:11:53 +0900 User-Agent: KMail/1.9 References: <20051211013550.66bfd7d2@snowdrop.home> <200512120844.00805.jstubbs@gentoo.org> <20051212000129.65f4e127@snowdrop.home> In-Reply-To: <20051212000129.65f4e127@snowdrop.home> 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: <200512120911.53976.jstubbs@gentoo.org> X-Archives-Salt: a1ef49f9-e88d-489f-a12b-6137630dceaa X-Archives-Hash: 42d7d6ee131f7d52feb259e7b322a721 On Monday 12 December 2005 09:01, Ciaran McCreesh wrote: > On Mon, 12 Dec 2005 08:44:00 +0900 Jason Stubbs > > wrote: > | Repositories will be user-labelled. However, all that readers need be > | concerned with is how to extract the repository name from the > | news.unread file and how to then resolve that to a directory name, > | regardless of how repositories are implemented. > > See, this is exactly why I'm not wanting to care about multiple repo > details at this point. There's no specification of how they work and > what exactly they're supposed to do, and to make matters worse the way > you seem to think they'll be handled is a really really bad way of > doing it. Regardless of what you think about the current plans for multiple repository support, the details that readers will need to know wont change. > | Even before multiple respositories are properly supported, I > | guarantee bugs about support for this in portage overlays. With the > | above, we would be able to add that support. Without it, all we can > | do is put a big CANTFIX. > > Overlay is not the same as multiple repository support. There's no difference as far as readers go. > | In that case, the data should probably not be in /var/lib/portage and > | definitely not specified in the GLEP. It has nothing to do with > | portage (the app) and isn't a requirement on readers. What if a > | reader wants to keep track of what date an item was read on? Or any > | other metadata? A new file would need to be created anyway due to > | format constrainst placed on news.read... > > Hrm. Does the GLEP need to cover how news readers that want to keep > track of whether or not the sysadmin was wearing pants last tuesday > should work too? Nope, which is why news.read shouldn't be specified. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list