Currently in LFS, there's a single entity &blfs-root; that points to www.lfs.org/blfs/. However, there are a few places in the book that contain specific links to BLFS pages: db, inetutils and shadow offhand. These end up hardcoding the rest of the path link. Something like:
<ulink url="&blfs-root;view/svn/security/cracklib.html"/> There are two things I'd like to address here. 1. We shouldn't always point to the svn version. When a stable book is released, it should probably point to the stable version of the BLFS book. Although, there could be a time lapse where this could be a bad idea, i.e. LFS-6.2 + BLFS-6.1. Still, if someone's following the stable LFS book, they probably don't want to get forwarded into the development version of BLFS. 2. More nitpicky, but we could easily absorb the view/$version part into another entity. I suggest the following two entity additions to general.ent: <!ENTITY blfs-version "svn"> <!ENTITY blfs-view "&blfs-root;view/&blfs-version;/"> We have a similar convention in the BLFS book for referring to the LFS book. Thoughts? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
