On 2/17/10, Randy McMurchy wrote:
> If the community's expectations are that we have the most current
> release of every package in the most recent BLFS book, then the
> expectations are too high and are unreasonable.
I agree.
I think the most important thing is that following step by step
in th
stosss wrote these words on 02/16/10 14:18 CST:
> This is why I would really like to see the book devs go to posting a
> snapshot only when there has been a change to the book.
You are making a mountain from a molehill. If you are so worried if
there has been changes, just look at the daily render
On Tue, Feb 16, 2010 at 5:12 PM, Agathoklis D. Hatzimanikas
wrote:
> On Tue, Feb 16, at 04:46 Chris Staub wrote:
>> If the book has an updated date and no Changelog entry for that day,
>> just check the svn log to see what was committed.
>
> I would like to say the same. It's easier to work with t
The issue is trying to hit a moving target.
>>> That is exactly the big problem!
>>> You will *always* be working on BLFS for more than 1 day.
>
> On 2/16/10, Ken Moffat wrote:
>> http://www.linuxfromscratch.org/blfs/downloads/svn/
>> OK, I admit it looks just like a load of patches, but with
