On 6/24/10, Timothy Rice wrote:
> It occurred to me that maybe once mysql is installed, info can then use
> mysql to, say, manage a database of entries, or something. Pure
> conjecture, but if true, it could explain why dir would need to be
> rebuilt. However, nothing I've noticed in any document
> True, considering the for statement just walks through the entire
> directory
> anyhow.
> ...
> Maybe there's another reason for walking through the directory, other than
> just taking the opportunity to catch any other missed dir entries?
It occurred to me that maybe once mysql is installed, in
On Wednesday 23 June 2010 21:32:41 Timothy Rice wrote:
> That is what I thought 'dir' was for, and I guessed that that is what
> install-info did. However, it does not make sense to me that the previous
> dir needs to be deleted first, before redoing install-info for all the
> packages already inst
Hi Trent,
> my understanding is that the dir file is
> a table of contents for the info program.
> ...
> If you skip this step I believe that you'll
> just be missing an entry for mysql on the
> default info page, but should still be able
> to issue 'info mysql'
> ...
> I'm pretty sure that mysql
On Wednesday 23 June 2010 20:09:58 Timothy Rice wrote:
> Still, I don't even understand why dir needs to be rebuilt. The following
> explanation in the blfs book is a little unhelpful:
> "pushd ... popd: This set of commands rebuilds the /usr/share/info/dir
> file as the installation failed to do s
Okay, thanks again for your help, Andy, Chris, and Mike. I think I have
discovered the source of my problems.
Basically, my difficulties are due to just blindly following the commands
in the blfs book. It isn't mysql itself that is trying to remove the 'dir'
file, it is my own build script; I didn
