On Sun, Dec 18, 2005 at 12:18:16PM +0200, Marius Mauch wrote: > Brian Harring wrote: > >On Sun, Dec 18, 2005 at 06:23:55AM +0000, Ciaran McCreesh wrote: > > > >>On Sat, 17 Dec 2005 21:50:47 -0800 Brian Harring <[EMAIL PROTECTED]> > >>| You haven't stated how the 'package manager' will trigger the user's > >>| reader of choice for these targets. Should also extend this to allow > >>| a way to disable any news notices, lest someone's cronjob get hung > >>| displaying news (feature or not, it's needed). > >> > >>The same way the package manager handles updating config files: it > >>won't. It'll just tell the user that some news items need reading. > > > > > >And you'll personally handle all of the bug spam from feature requests > >that --ask trigger $news_reader? > > > >It's a logical extension, thus people will ask for it. > > I don't think so. > How many people have asked for etc-update integration?
etc-update style notices are at exit of emerge. This proposal has news item warnings prior to the merge actually occuring (no specification of sleep however). Different scenario, thus etc-update isn't a good indicator. > To quote myself: > "Granted race conditions might be an issue (where the solution > complicates tools), but that's so minor I wouldn't really care about > it." > That I wouldn't care about it isn't a general recommendation to ignore > the issue. Yes, for a perfect solution it is required, but do we aim for > a perfect solution? We do if it potentially allows for 'critical' news to be unseen, at least imo. > Another new issue nobody has mentioned yet: > The GLEP doesn't say anything about file permissions/ownership as in who > will/should be able to a) read news and b) modify the news-* files. > Without thinking too much about it I'd say a) users in portage group and > b) root. *cough* good point. ;) ~harring
pgpacHFQeelTO.pgp
Description: PGP signature
