#427 closed defect (invalid)
entity fix in chapter05
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | minor | Keywords: | |
Cc: |
Description
LFS/BOOK/chapter05/gcc-inst.xml: "gcc-&gcc-version;-nofixincludes-2.patch" instead of "gcc-3.2-nofixincludes-2.patch" Patch attached.
Attachments (1)
Change History (5)
by , 22 years ago
Attachment: | lfs-ch05-entity.patch added |
---|
comment:1 by , 22 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
I did that on purpose. I'm not sure if that patch is going to stay past a future release or not. Say we upgrade to gcc-3.2.1 one day and the fixnoincludes-2.patch stays in effect, then we don't have to change the version number of GCC in more than one place. We'll just have to do it in the entities/gcc.ent file.
I agree it's a bit of a kludge, but that's all this patch is anyways so it's right in line (somehow)
comment:2 by , 22 years ago
attachments.isobsolete: | 0 → 1 |
---|
comment:3 by , 22 years ago
Resolution: | invalid |
---|---|
Status: | closed → new |
Then I suggest that LFS/BOOK/chapter03/gcc-patch.xml has to be changed to: ... GCC nofixincludes Patch (3.2) - 1 KB: <ulink url="&ftp;/gcc-3.2-nofixincludes-2.patch.bz2"/> <ulink url="&http;/gcc-3.2-nofixincludes-2.patch.bz2"/> Because, as you said, when LFS upgrade to gcc-3.2.1, we will not have broken links ;)
comment:4 by , 22 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Patch was removed today, this bug isn't valid anymore because of it.
"gcc-version" entity fix