-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/03/2013 12:06 AM, Michał Górny wrote: > On Wed, 02 Jan 2013 19:49:02 -0800 > ""Paweł Hajdan, Jr."" <phajdan...@gentoo.org> wrote: > >> It came up again with <https://bugs.gentoo.org/show_bug.cgi?id=449918>, >> and I think it's worth to think about a better fix. I still keep hitting >> mysterious collisions with orphaned files from time to time. >> >> How about switching the developer profile from collision-protect to >> protect-owned, and proceeding with enabling protect-owned by default for >> all profiles? (not all developers are using the developer profile) > > Well, it all depends. > > protect-owned is easy and lazy. You just get errors on package > collisions, care about nothing else. > > collision-protect cares about every collision. It can help you notice > that *your* package lefts orphaned files for some reason or writes > where it is not supposed to write. > In the years I ran collision-protect I can say it prevented hundreds of merges of linux-firmware (because the kernel also installs firmware) and not much else.
Would you be able to share more specific insight on how collision-protect helped protect files that need to be protected where protect-owned would have been inferior? - -Zero -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQ5RZIAAoJEKXdFCfdEflKUxIP/1OApovsseVqUhIPPCQB1Z08 Yua5b2ripFwh/190eqNqvRFStp+K8ZChMMbfhjdjr3kzrqhpvOYHoM6/fdyz8yeC BqOXfTg+wrHkPl5ql1YMv8ZHs8VrGF7ZIRMcwiylS0GaftPwIh1i0nD2ZYEEKhyz FlIY9ZzX4dnKtNXeEahDTu38aLIwF0XWCcPcIOEtFEnaNjgmxVR1ZRmXk1ynB/VQ XYaHNTL6irxA/YkImQR4JCBOAZKyjLZzy6vbLqsjic+MAzpfklmgVebnBY6hWkxK FKfz13Gt9EWno3b0tTDa+OYrVMw0Z84GpMWPILCfChI3YcSj+ODi5ql2yM4avAiU t7lQCTzOYfKCSZOXwAiN65DJL+ssq3DX3kJfA5/uyRmsJfGYMd2M9/F3lbmxhquN lbzhzaJQyyPMCXmsKcKiAAioOL8FhP5jYjuYsH2b6XlCkNC7BB1TaY2FOlvoyZPF 50z31AguddD7ylofVKojU2BPJKF4pKPub5qy+hb0wyCmjEuNjp0W6t20azOZMNM/ LxPLLd7s6+YbgbS1pIbEWPwe2U1bHpkvb2RHZ8tPzCAvtlkT5LcUzV3OdHgZ3kxh Z1hHPTCZJx+7y4aQFJAXvUx0RpnXQ92MsPPMeFGl/j4oIjNvphRlYR9wctDskWst ECOuGbPwMI+PCq1K3DWk =DY2e -----END PGP SIGNATURE-----
