1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 04/11/2013 03:03 PM, Matt Turner wrote: |
5 |
> On Thu, Apr 11, 2013 at 11:53 AM, Rick "Zero_Chaos" Farina |
6 |
> <zerochaos@g.o> wrote: |
7 |
>>> Not sure this is the way to go. I'll have to think through the |
8 |
>>> implications. Consider your stage1 build dies with some stupid tree |
9 |
>>> breakage that you can fix in your portage snapshot and restart the |
10 |
>>> stage build. This is going to cause your stage to rebuild everything. |
11 |
>>> |
12 |
>>> Wouldn't disabling the use of binary packages during the seed stage |
13 |
>>> update fix this? |
14 |
>>> |
15 |
>>> |
16 |
>> I'm not sure I'd call rebuilding it every time a "fix" when you just |
17 |
>> rejected deleting the bad packages and rebuilding ONCE. |
18 |
> |
19 |
> I'm not sure what you mean. |
20 |
> |
21 |
> Updating the seed stage should only ever happen once. If that fails |
22 |
> and you don't have binary packages to fall back to on restarting, I |
23 |
> think that's an okay price to pay. Especially since it happens early |
24 |
> enough in the process and avoids potential problems that are only |
25 |
> noticed at the beginning of stage2. |
26 |
> |
27 |
> Oh, and if updating the seed stage fails... it was only rebuilding gcc |
28 |
> dependencies anyway. That's not so bad at all. (I don't care about |
29 |
> custom update commands and isn't something that we can fix) |
30 |
> |
31 |
>> As I said, the only proper fix is to update the toolchain to EAPI5. We |
32 |
>> could live in the dark ages forever, but I really don't think it helps |
33 |
>> anyone. |
34 |
> |
35 |
> That seems like a potentially good long term goal, but isn't something |
36 |
> that we can force through. |
37 |
> |
38 |
> |
39 |
We already don't BUILD any new packages during update_seed. Originally |
40 |
we did, I encountered issues and fixed it in |
41 |
e7ea409acb52b43e9ea141c57201f9f87673f7ba to prevent building of packages |
42 |
during update_seed. |
43 |
|
44 |
Thanks, |
45 |
Zero |
46 |
-----BEGIN PGP SIGNATURE----- |
47 |
Version: GnuPG v2.0.19 (GNU/Linux) |
48 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
49 |
|
50 |
iQIcBAEBAgAGBQJRZwxpAAoJEKXdFCfdEflK3qsQAKuklF3DkQ2vJPoYMy2KWo0H |
51 |
4+YRfH/zgkhnemqgzgbr3eIuY/A1nccIZ89buwua4Gni2gnXdya6gPDkgMTkGvzY |
52 |
jlHRdSg5+MFgju5OA/peYCoAAz3TU/CP1U8OVJhPZ35R1v3nRVcBlI60jwXCIvqP |
53 |
LQEur9b2Mdx+p7er3QKypjJNtPNRYxZBoEicKXsIfIcvQRWnsrpnS9xxktGlrukE |
54 |
+eYTWnAB8gYmjQp2n6ZGT3aTuQoDgomBUTIeTmsAzz+U+MafSItnWBI+4w9s4auV |
55 |
93ac65u/7Yrey7hLf9V1KP9T1xEGavWgeSy1e2w7a/QAsXdmEpCi1+ai9Bu8j+JU |
56 |
RL0PkdcWyfEPdgSLAxvhj8LzEovnGn6c74Vu6larOQOOOQWPal+pq6JwJR1zxoVm |
57 |
WBQsyjPTsBuPoWn4L8vLKwqiHNBPw5jzdpTlADvAm0ET2pQ73fV/gYCHIzwtwPYo |
58 |
CxHQasxgS/qE/ZD/aoOWzroQ5z6r/8BtOFNhmM5cj2H1rFi/nsKQyZDlR5nA7A1Z |
59 |
akjQb/aQI+RAERa6acGttmldRkP3dWnjycRJpoVfpg1XJFdwJKSyzfmuU7slFL88 |
60 |
I+2B0e+3Aluog45rGiLcXDHZASdZ/RDRqvIrovLw+hoy5Koo6KRGitjLNWEP6F+f |
61 |
E7OoClVdEKD5MCVrZL65 |
62 |
=Iqpi |
63 |
-----END PGP SIGNATURE----- |