Randy McMurchy schrieb: > The easiest and best way to keep track of changes is to subscribe to > LFS-Book and read the commit messages. If it ain't there, then it didn't > happen.
depents on how you define "easy". i agree the log is complete. absolute. each and every change is logged. but easy?? as i wrote, i checked the chapter "changelog" to see what changed (once every few days or just once a month, depending on my other interests). i really like the work you do (and i guess here is a good place to say THANK YOU ALL FOR YOUR GREAT WORK!). but i don't have the time and/or skills to decrypt all the messages running throu the *-book lists. i'm really happy to have some systems for which i'm responsible out in the wild where i really understand what happens (and why which package is installed). the "changelog" is exactly the tool which serves my needs. i'll follow the wiki log for a while to see wether it will suit even better. but maybe there is to much "noise" for my poor eyes. for me as a lower skilled user i'm seeking for a possibility to follow your (where you adresses all authors/contributors) path on an easier way. "easy" as my personal interpretation means ;). thus i probably will follow the lfs-book, but for blfs where i use just a few packages (non of the systems has X installed as they are just file-, print- and webservers) i guess there will be to much information i don't need. my last compile was quite up to date, except inetutils in the old place and i had no errors with the build. now i hardly dare to ask my next question: *WHY did you move inetutils?* tobias -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
