On 2/9/2020 11:33 AM, Pierre Labastie via lfs-dev wrote:
Le 09/02/2020 à 17:46, Bruce Dubbs via lfs-dev a écrit :
On 2/9/20 10:36 AM, Pierre Labastie via lfs-dev wrote:
Le 09/02/2020 à 09:02, Kevin Buckley via lfs-dev a écrit :
I'll spare you the details of how I cam to notice this but i was just
applying some local patches to the most recent trunk Rev 11745
and realised that
Chapter 5 still has these two XML files in the source directory
gmp.xml
mpfr.xml
Add e2fsprogs.xml and flex.xml to this list...
even though they are no longer rendered, nor referred to, in the Book.
Similarly, in Chapter 6, these four no-longer-rendered XML files are in
the source directory
db.xml
module-init-tools.xml
pcre.xml
popt.xml
Maybe they could be removed from the SVN ahead of the upcoming release ?
Other files that used to slumber there (ed.xml) have been given the boot.
Also dedication.xml in prologue is not used anymore.
Other weird things are the id attributes, where pre-xxx occurs in chapter 2,
ch-tools-xxx occurs in chapter 4 and chapter 6, etc. I'd suggest the following:
-for chapters, id's are of the form chapter-xxx, where xxx may be composed of
several words.
- for sect1, form the id's as follow, ch-yyy-zzz, where yyy is the last word
of xxx for the parent chapter, and zzz may be ad libitum, but of course
related to the section title...
- use pre-zzz for sections in the prologue
I can make this clean up (removing unneeded files and refactor id's) if you
agree.
Those unused files are still around because when we removed them, we were not
sure if we wanted to put them back. I'm not sure they hurt anything, but what
we can do is create an archive directory like in BLFS and move them there.
I'll point out that there are probably several files in stylesheets that are
not used, but are a part of docbook.
I'm OK with you doing a cleanup if you really think we need to do that.
Well, I agree it is not a big deal. It may be annoying when doing batch
modifications (something like "vi chapter05/*.xml"). Reinstating those files
would be easy, since they are present in the other chapter or in blfs, so I do
not think we need to archive them.
Side note (off topics): the archive directory in blfs is
becoming very big, and increases the time for downloading/checking out the
book. Maybe we could have a policy of removing files older than two years or
so, since it is unlikely that those files become needed again, in their
archived form at least.
There really isn't any need for the archive directory. We are in version
control. It's not that difficult to go back a book release or two and
find where a package was removed.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
