Dan Nicholson wrote: > On 4/20/06, Dan Nicholson <[EMAIL PROTECTED]> wrote: >> On 4/20/06, Randy McMurchy <[EMAIL PROTECTED]> wrote: >>> It has been customary to put run-time only dependencies in its own >>> section, or (as I believe Bruce prefers) in the configuration section. >> OK. What about this. > > Tracking down the run-time dependencies uncovered a whole bunch more > run-time configuration files. I also realized that there are useful > docs that should be installed and another install target to install > two useful configuration files. Since there are quite a few changes, > I've rendered it locally at > > http://anduin.linuxfromscratch.org/~dnicholson/blfs/basicnet/tin.html > > and attached the diff. Could you guys please review this before commit?
I haven't looked, but go ahead and commit. Its just as easy to update and render locally as to look at another site. Don't be afraid of committing something to trunk that you are not sure of. We can always change it later. We will be a little more careful when we create a -testing branch. > One question I have is about /etc/mailcap. It's a general > configuration file, not just for tin. From the mutt man page: > > /etc/mailcap > System definition for handling non-text MIME types. > > Should this be on the tin page? Sure. If it's installed or used by tin, then it should be there. Just because something else may use it, doesn't mean it shouldn't be there. For instance, look at postfix. It has an entry for sendmail. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
