>>>>> On Sat, 16 Jan 2016, Michał Górny wrote: > That doesn't really make sense to me. There is no real urgency in > getting the new format right now, and omitting the most important > issue is not really the solution here.
The idea was to introduce EAPI 5 dependencies for the Display-If-Installed header. Anything else is an added bonus at this stage, and can be included if it is trivial to implement. Nothing prevents us from creating a format 2.1 or 3.0 later for any features that will take more time. Or, if we are thinking in long time scales, we could even incorporate the news item spec into PMS with the next EAPI (and replace the format number by the EAPI). >> The problem with any visibility filtering is that visibility >> depends on user configuration [1], and I don't know what changes in >> the package manager would be necessary to make this work correctly >> and efficiently. For example, how does portage's --autounmask-write >> option interact with it? > Leave solving this to Portage developers. Autounmasking is not > something you do often on stable systems, and we have better QA to > avoid issues that could require it. Yeah, if I wasn't sure about Display-If-Visible, then this statement would finally convince me that we should skip that feature, for the time being. That something does not happen often is no excuse for not having an implementation that can handle such rare cases. Ulrich
pgpkB_SqJV8ZT.pgp
Description: PGP signature
