Opened 10 years ago
Closed 10 years ago
#3645 closed task (fixed)
Update text on packagemanagement page
Reported by: | rt | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.6 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
The current package management page (6.3), in the section on upgrading the toolchain, states
For micro version updates, a simple reinstallation usually works...
it then gives an example for upgrade of glibc 2.3.4 to 2.3.5. Glibc no longer has micro versions (neither does binutils), so wouldn't GCC be a better example to give in this regard?
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
I have also updated major versions of glibc, gcc and binutils on a running system without problems.
Version 0, edited 10 years ago by (next)
Note:
See TracTickets
for help on using tickets.
We need to think this through a bit. I've updated both gcc and binutils on a system without problem. The only time I really feel compelled to rebuild everything for cause (e.g. not testing a new release of LFS/BLFS) is when package updates require a new glibc. I've only had that happen once in about the last 10 years.
I believe others have updated glibc too, but that's a bit trickier.