On Monday 12 December 2005 02:43, Ciaran McCreesh wrote:
> On Sun, 11 Dec 2005 13:32:05 +0900 Jason Stubbs <[EMAIL PROTECTED]>
>
> wrote:
> | Repositories will definitely have a unique identifier. Perhaps it
> | would be better to use the repository-identifing format from the
> | beginning so that readers are forced to be forwards-compatible?
> | Assuming the readers would then output the repository name, labeling
> | it "gentoo" should work well...
>
> *shrug* If someone creates metadata/repository_id (or whatever), I'll
> go with that. Otherwise, I'm not in favour of attempting to guess how
> the thing will be implemented.

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.

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.

> | > When a news item is read, its name should be removed from the
> | > ``news.unread`` file. News clients may add the name to a
> | > ``news.read`` file in the same directory with the same file format.
> |
> | news.read should either be mandatory or not created at all. Should a
> | user change from a reader that creates and uses the file to one that
> | doesn't and then change back again the results will be unexpected.
>
> I'm not sure that that's the case. With a news to email forwarder, for
> example, it wouldn't make sense to keep track of news.read.

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...

--
Jason Stubbs
-- 
gentoo-dev@gentoo.org mailing list

Reply via email to