| 1 |
On Tue, Sep 29, 2020 at 1:48 PM n952162 <n952162@×××.de> wrote: |
| 2 |
> |
| 3 |
> 10 weeks ago, I updated my system and it took days to build. I just |
| 4 |
> started a new update of my system, and it looks like it will take at |
| 5 |
> least more than a day again ... |
| 6 |
> |
| 7 |
> Why is gcc being rebuilt after 10 weeks, for example? |
| 8 |
|
| 9 |
Your email is a bit vague on details. |
| 10 |
|
| 11 |
gcc has 4 slots that are stable and 1 slot that is ~arch. You usually |
| 12 |
only need one of those installed, but could have more than one, and at |
| 13 |
various points there can be updates to any of them. |
| 14 |
|
| 15 |
I wouldn't say that gcc is updated frequently on my stable systems, |
| 16 |
but 10 weeks is a pretty long time. Looking at genlop I have updates |
| 17 |
on: |
| 18 |
Sun Apr 19 11:21:44 2020 >>> sys-devel/gcc-9.3.0 |
| 19 |
Fri Jul 10 07:35:45 2020 >>> sys-devel/gcc-9.3.0-r1 |
| 20 |
Sat Aug 8 06:56:05 2020 >>> sys-devel/gcc-9.3.0-r1 |
| 21 |
|
| 22 |
I'd have to do some digging as to why gcc was rebuilt in Aug. gcc |
| 23 |
rebuilds are annoying since it takes so long (in part because it has |
| 24 |
to be built twice). However, I think the maintainers do try to |
| 25 |
minimize it within reason - 3 builds on such a key package YTD isn't |
| 26 |
bad. Nobody is going to be able to promise you that gcc won't get |
| 27 |
rebuilt only once a year/etc. |
| 28 |
|
| 29 |
-- |
| 30 |
Rich |
Archives