Re: MySQL and More Control/Package Users Package Mgmt
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, 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 documentation for either mysql or info suggests that this is actually true. Now, if nothing like that is really going on, then may I submit to the BLFS editors that the suggested install commands for mysql be streamlined and simplified? If the walk through the entire directory is just to pick up any info files that have been missed to date, then I don't think that should be part of the mysql install. It would be more appropriate to put such tidying up in a module of its own. Well, thanks for your time, Trent, and everyone. Cheers, Tim -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MySQL and More Control/Package Users Package Mgmt
On 6/24/10, Timothy Rice t.r...@ms.unimelb.edu.au 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 documentation for either mysql or info suggests that this is actually true. Now, if nothing like that is really going on, then may I submit to the BLFS editors that the suggested install commands for mysql be streamlined Info is documentation that I personally only consult as a last resort. Everything that installs any info documentation apparently updates that file called dir. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MySQL and More Control/Package Users Package Mgmt
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't notice this because I just
unreflectively copied and pasted:
\begin{code}
pushd /usr/lib
ln -v -sf mysql/libmysqlclient{,_r}.so* .
popd
pushd /usr/share/info
rm -v dir
for FILENAME in *; do
install-info $FILENAME dir 2/dev/null
done
popd
\end{code}
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 so.
Yeah, I just don't get that. Saying the installation failed to...
implies that the installation ideally should, for some reason, but
doesn't. So why should it? What would be the consequences of skipping
these rebuild commands?
Given that rebuilding dir really is necessary, should I rebuild both
/usr/local/share/info/dir and /usr/share/info/dir, or just one of them?
Cheers,
Tim
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: MySQL and More Control/Package Users Package Mgmt
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 so. Seems clear enough to me. I did have to read the man page for install-info, which doesn't seem to say what a dir file is for, ha. Anyhow, my understanding is that the dir file is a table of contents for the info program. Yeah, I just don't get that. Saying the installation failed to... implies that the installation ideally should, for some reason, but doesn't. So why should it? What would be the consequences of skipping these rebuild commands? 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' Given that rebuilding dir really is necessary, should I rebuild both /usr/local/share/info/dir and /usr/share/info/dir, or just one of them? FWIW my /usr/local/share/info/dir is empty... but I'm pretty sure that mysql only gets dumped into one folder, and that is the folder you should rebuild the dir file in. -- Regards, Trent. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: MySQL and More Control/Package Users Package Mgmt
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 installed. True, considering the for statement just walks through the entire directory anyhow. Assuming the mysql package user does have write permissions to `dir', why is it not sufficient to simply run a command such as the following?: install-info mysql.info dir 2/dev/null I'm afraid I don't have an answer, you may just have to play around and see if the same dir file gets produced. Toying around here, though, your suggested command seems to produce the same dir file as the for statement. Maybe there's another reason for walking through the directory, other than just taking the opportunity to catch any other missed dir entries? -- Regards, Trent. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
