Arfrever Frehtes Taifersar Arahesis <arfre...@gentoo.org> posted 200905211957.55040.arfre...@gentoo.org, excerpted below, on Thu, 21 May 2009 19:57:49 +0200:
> 2009-05-20 20:00:43 Ciaran McCreesh napisał(a): >> On Wed, 20 May 2009 19:12:56 +0200 >> Arfrever Frehtes Taifersar Arahesis <arfre...@gentoo.org> wrote: >> > This error occurs only when there is no up-to-date cache for given >> > ebuild. rsync users would see only the usual "masked by: EAPI 3" >> > message. >> >> We always have to assume that there might not be an up to date cache. >> The Gentoo rsync mirrors do not always ship up to date cache, >> particularly if someone's just changed a widely used eclass. > > Users can wait an hour and run `emerge --sync` again. Anyway, Portage > still allows to install other ebuilds (with lower EAPI) of given > package, so this corner case doesn't need to slow down progress. Except that users are STRONGLY encouraged (on threat of ban) from syncing more than once a day. A 24-hour wait can seem like a long time, especially when you're doing your weekly update on your one off day a week, so it's effectively a 7-day wait, or you were updating your folks computer on holiday and it could be a multi-month wait, or when something's broken that you're depending on to make that presentation in the morning and you know the new version fixes it because the bug said so. If we're going to be saying wait an hour, then let's get rid of the wait 24-hours thing. Otherwise, that's mixed messages to users and as Ciaran points out, users get confused by such things. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
