1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 30/06/12 11:16 AM, Mike Frysinger wrote: |
5 |
> On Saturday 30 June 2012 07:22:39 Zac Medico wrote: |
6 |
>> On 06/30/2012 04:07 AM, Pacho Ramos wrote: |
7 |
>>> I would like to discuss a bit more issues like: |
8 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=423087 |
9 |
>>> |
10 |
>>> Even if there are "a lot" of packages that can cause this |
11 |
>>> breakage when downgraded, I think it should be prevented and |
12 |
>>> package managers shouldn't try to downgrade this kind of |
13 |
>>> packages as they will later cause a total breakage. People is |
14 |
>>> not supposed to know that downgrading some package system will, |
15 |
>>> for example, have an unusable gcc. |
16 |
>> |
17 |
>> It seems like a die in pkg_pretend would serve pretty well. |
18 |
> |
19 |
> doing it on a per-ebuild basis doesn't make much sense. a simple |
20 |
> version compare (like we do in glibc as an exception to this rule |
21 |
> because of its much wider implication) is incorrect: the new |
22 |
> version might not introduce any new symbols compared to the old |
23 |
> one, and even if it has, other packages might not have been linked |
24 |
> against the new symbols. -mike |
25 |
|
26 |
Instead of preventing downgrade wouldn't it make more sense to figure |
27 |
out a way to force a rebuild on @system or @toolchain or whatever bits |
28 |
are broken as soon as the downgrade occurs, rather than just making it |
29 |
a one-way ticket? If we could sort this out (and sub-slots may help |
30 |
with this, but probably we'll need some extra work too) then we could |
31 |
probably support switching from ~arch to arch at a whim.. Not |
32 |
necessarily a bad goal. |
33 |
|
34 |
|
35 |
-----BEGIN PGP SIGNATURE----- |
36 |
Version: GnuPG v2.0.19 (GNU/Linux) |
37 |
|
38 |
iF4EAREIAAYFAk/vNKcACgkQ2ugaI38ACPDDgQD/XhgB1G6rIYXuhR/EnJDLyfgL |
39 |
NKfW6TifMcJr9wHFNooA/2RDkxOSFePAHy81IxGWfjvpb2wNw4b/IzDwK8u4hcAS |
40 |
=Q3Wd |
41 |
-----END PGP SIGNATURE----- |