Opened 17 years ago
Closed 16 years ago
#2175 closed task (fixed)
M4-1.4.11
Reported by: | Jeremy Huntwork | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New version, see: http://lists.gnu.org/archive/html/m4-announce/2008-04/msg00000.html
Attachments (1)
Change History (11)
comment:1 by , 17 years ago
comment:2 by , 16 years ago
Any resolution on this?
Ticket was opened 2 months ago but still we haven't taken any decision on this and the change is completely transparents as it doesn't need any kind of change in the installation instructions.
Comments?
Julio
comment:3 by , 16 years ago
And here would be a perfect opportunity for you to flex your technical muscles and prepare a patch for the book's source. ;-)
Have a look here for help editing the book: http://wiki.linuxfromscratch.org/~jhuntwork/lfs-editor-manual
The Editor's Manual is a little old (hasn't been touched since 2006) but the book's structure hasn't changed much, so most of the info there is still relevant.
follow-up: 5 comment:4 by , 16 years ago
Thanks for the info, I'll try to flex my muscles and see the result, although in the meantime, would be nice if we just apply these changes (at least while I try to actually produce more than tickets and *pings* _)
(not to mention I don't have an account in the belgarath server, so I cannot use the svn facilities for the moment :P)
Julio
comment:5 by , 16 years ago
Replying to LydianKnight:
(not to mention I don't have an account in the belgarath server, so I cannot use the svn facilities for the moment :P)
I know you don't have an account, in part because 'belgarath' isn't being used anymore, but also because our dev team is small enough that it's easy to keep track of. However, you can still use anonymous svn to check out a local copy and then produce a patch from the changes you make. Once you have a patch you can submit it, either as an attachment to this ticket or to the lfs-dev list, and a current editor will review it and apply it to trunk.
Doing this does two things:
- It expedites edits to the book (because sometimes a current editor doesn't have time or energy to sit down and do the grunt work).
- As you get known by the community and your patch submissions are found to be useful, at some point you may be invited to help edit the book yourself regularly and our development team grows.
comment:7 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Tickets should not be closed as fixed until the changes are incorporated in the book.
comment:8 by , 16 years ago
Milestone: | 7.0 → 6.4 |
---|
comment:10 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
This ticket is not ready to be closed as we are still undecided about where to put it in Chapter 5 (if at all), or should it be made a prerequisite. Again, held open as a reminder.
comment:11 by , 16 years ago
Status: | new → assigned |
---|
comment:13 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Updated LFS to M4-1.4.11
Also added M4 to Chapter 5 right before the GCC Pass1 installation.
compiles just fine without any error or needed instruction modifications, hence I recommend closing this ticket, as it just works ;)
Julio