Re: Some LFS 6.5 - 6.6 Inconsistencies
On Mon, 2010-06-07 at 17:45 -0500, Bruce Dubbs wrote: That's not so easy. We create the book with Docbook xml. I don't know of a way to to do that. We do have both a change log and a What's new section. We are trying to do a new release every 6 months. If you look at What's new, almost every package changes each time, but most use the instructions unchanged. Yeah, I generally work off the Changelog page when updating the scripts I build everything with, working up the list from whatever date I last built against. Works for me - Changelog open in one tab, and the index in a second one. Simon. signature.asc Description: This is a digitally signed message part -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Some LFS 6.5 - 6.6 Inconsistencies
That's not so easy. We create the book with Docbook xml. I don't know of a way to to do that. We do have both a change log and a What's new section. We are trying to do a new release every 6 months. If you look at What's new, almost every package changes each time, but most use the instructions unchanged. Yeah, I generally work off the Changelog page when updating the scripts I build everything with, working up the list from whatever date I last built against. Works for me - Changelog open in one tab, and the index in a second one. FYI. This link might be useful: http://www.sagehill.net/docbookxsl/Changebars.html -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Some LFS 6.5 - 6.6 Inconsistencies
Neal Murphy wrote: That's not so easy. We create the book with Docbook xml. I don't know of a way to to do that. We do have both a change log and a What's new section. We are trying to do a new release every 6 months. If you look at What's new, almost every package changes each time, but most use the instructions unchanged. Yeah, I generally work off the Changelog page when updating the scripts I build everything with, working up the list from whatever date I last built against. Works for me - Changelog open in one tab, and the index in a second one. FYI. This link might be useful: http://www.sagehill.net/docbookxsl/Changebars.html Thanks. That may be doable, but it looks like a fairly significant effort to get all the details right. The html doesn't support change bars, but changes can be highlighted in color/underlining, etc. My thought would be to to show additions and changes, but hide deletions. I added a ticket at low priority so we don't forget about this. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Some LFS 6.5 - 6.6 Inconsistencies
Tim Burress wrote: Hello, I've just finished upgrading from LFS 6.5 to 6.6 and there were a few small inconsistencies I noticed along the way: (1) When building make, the book calls for a patch called make-3.81-upsream_fixes-1.patch, but this is not available in the FTP archive (or at least the mirror I used). It's there at http://www.linuxfromscratch.org/patches/lfs/6.6/make-3.81-upstream_fixes-1.patch (2) When building perl, the book calls for a utf8 patch to avoid a segmentation fault, but the patch is not available in the FTP archive. By contrast, there is a libc patch in the archive that isn't in the book. Maybe it's just a file naming problem? http://www.linuxfromscratch.org/patches/lfs/6.6/perl-5.10.1-utf8-1.patch (3) When building e2fsprogs, the book calls for version 1.41.10 but the FTP archive has 1.41.9. Meanwhile the e2fsprogs people recommend 1.41.12, and the bug list is frightening enough that I just used that. OK, I'll fix up the mirror master. And that's about it. One suggestion is that it would be REALLY, REALLY convenient if future versions of the book had change bars to indicate which parts were modified from the previous edition. There's a lot of detailed sed hackery, etc, and it would be good to be able to see at a glance when that's been changed (or not). That's not so easy. We create the book with Docbook xml. I don't know of a way to to do that. We do have both a change log and a What's new section. We are trying to do a new release every 6 months. If you look at What's new, almost every package changes each time, but most use the instructions unchanged. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Some LFS 6.5 - 6.6 Inconsistencies
Hello, I've just finished upgrading from LFS 6.5 to 6.6 and there were a few small inconsistencies I noticed along the way: (1) When building make, the book calls for a patch called make-3.81-upsream_fixes-1.patch, but this is not available in the FTP archive (or at least the mirror I used). (2) When building perl, the book calls for a utf8 patch to avoid a segmentation fault, but the patch is not available in the FTP archive. By contrast, there is a libc patch in the archive that isn't in the book. Maybe it's just a file naming problem? (3) When building e2fsprogs, the book calls for version 1.41.10 but the FTP archive has 1.41.9. Meanwhile the e2fsprogs people recommend 1.41.12, and the bug list is frightening enough that I just used that. And that's about it. One suggestion is that it would be REALLY, REALLY convenient if future versions of the book had change bars to indicate which parts were modified from the previous edition. There's a lot of detailed sed hackery, etc, and it would be good to be able to see at a glance when that's been changed (or not). Thanks! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
