-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya,
On 06/02/15 08:48, Duncan wrote: > Daniel Campbell posted on Thu, 05 Feb 2015 22:55:05 -0800 as > excerpted: > >> As a user and prospective developer, why? Transparency is >> important to open communities like Gentoo's, and reading the >> discussions can give users and developers alike some context that >> they wouldn't normally get if they hadn't seen the >> discussion(s). > > (As a user myself...) I believe he's referring not to the technical > disagreements themselves, but to the practical effects on users of > unmasking, remasking, unmasking, changing USE flags, changing the > / meaning/ of USE flags, changing USE flag defaults... before a > final plan of action is settled on. Duncan was absolutely right, and I communicated myself poorly. I have no issue with them discussing the best course of action. I positively would like to get this situation resolved as quickly as possible! I was concerned that a warning which had been in place in package.mask since September was removed by a different developer than the one who put it in place, and that a package was unmasked (while a USE flag was masked) which then forced everyone who read the portage news article and swapped mplayer to mpv based on the article, to then be told they have to rebuild with ffmpeg after all, and potentially rebuild a lot of other packages because of that. The mask of the USE flag even removed the possibility of building the newer mpv with libav, even though it's actually possible (so users who'd unmasked >=libav-10, could no longer build mpv-0.7.x when the had previously). I don't care which way it gets sorted out, but having such direct effects on users, without agreement or even discussion of the action beforehand is what I'd like to avoid (and then poorly phrased as "airing in front of the users", for which I apologize)... Mike 5:) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0 iKYEARECAGYFAlTVc7tfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldEZGQjEyM0ZDRDBCRjcwREE1MzA0MjNBREJC QkFENkEyNkMyMDE1N0EACgkQu7rWomwgFXqPrgCfdyve0LLT1eeMPTo8+sPaLs7s 4TYAn2joniuA4LOPbU03XRLBXoh7gWX/ =lSq2 -----END PGP SIGNATURE-----
