Gentoo Archives: gentoo-dev

From: "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] collision-protect -> protect-owned ?
Date: Thu, 03 Jan 2013 04:01:41
Message-Id: 50E50288.3030809@gentoo.org
In Reply to: [gentoo-dev] collision-protect -> protect-owned ? by "Paweł Hajdan
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 01/02/2013 10:49 PM, "Paweł Hajdan, Jr." wrote:
5 > It came up again with <https://bugs.gentoo.org/show_bug.cgi?id=449918>,
6 > and I think it's worth to think about a better fix. I still keep hitting
7 > mysterious collisions with orphaned files from time to time.
8 >
9 > How about switching the developer profile from collision-protect to
10 > protect-owned, and proceeding with enabling protect-owned by default for
11 > all profiles? (not all developers are using the developer profile)
12 >
13 > Paweł
14 >
15
16 I've been using protect-owned for months if not years with no issues at
17 all. collision-protect is a broken implementation, the way it always
18 should have been was as protect-owned is.
19
20 Protecting unowned files is silly, it only matters when two packages
21 collide.
22
23 - -Zero
24 -----BEGIN PGP SIGNATURE-----
25 Version: GnuPG v2.0.19 (GNU/Linux)
26 Comment: Using GnuPG with undefined - http://www.enigmail.net/
27
28 iQIcBAEBAgAGBQJQ5QKIAAoJEKXdFCfdEflKB+8P/3IG6e2yuDH/zGp+PXqRI0YH
29 cUEFw/L1hw8wvOp/rGgLDC0l8JSZTF8gzsiK5IG6ur3JR0+K/dLejR71ug1uPxo0
30 Vh5Rbq4QrWDWjw/KMhq2pvdVnCY7aK1y0er82vSx49k7bXXuNV3UMnDHP3GnZ/fT
31 w2cji4GT1cO96Ut2tjDRmUebcqcC0rd2eH2MnvewYvOnTuti14P4/1Z4Ur5p+tkf
32 +1yQTp+8ZNjSStAnxsuR5UjNE1b9Exr2+O8wPg5sC2H6fFqjVJjJ+BPA/KlKTVZw
33 mEoSq0+DjGH9ETsPj4/tLUztXf5H6DomT8BBEAPHuZF/WNBShmhyfv4R6iiQjD5v
34 bElSzjjbn5HfViprW9BmZ96xZCOw8FMWb2kuquVefWybGj+F4mI4LN4viBVXdNvf
35 y5vx3/fF9sPuu7wcyWCaHUjV2Nn3fa6CZebxOVXXr5KOMI6OpapIwasRZw+YZehD
36 pz5+FRCPAHixTixZL+AZIxzwuJuTA7EQlolwZ4EiW3jEVmbLQ+vClTFgxDNmDfAz
37 GqL5LsUY5wMcBKjusWoTJO4bx1A5Jnhz9p5xWQgfsvO4j8SycIq855jVTQ9TKpWF
38 rcDMFUyyCDRraLpplm6EWssCiscPrVXjxRlkdbIKMgSf4msMM6h1fVKg5WTeJwbN
39 q5QL1VtGtGccPS/7khtC
40 =Ljgj
41 -----END PGP SIGNATURE-----