Bruce Dubbs wrote these words on 01/24/07 10:57 CST:

> I'd give it another day and release the alpha tomorrow.

I'll see how my time goes today. I sort of had today outlined for BLFS
work, and tomorrow is really spoken for. I'm seeing issues with the
patch list, I'm trying to work it out now. Apparently, the code that
used to be in place that automatically checked for 'missing' patches
is no longer in place.

I just generated a patch list using the Makefile target and it seems
to be messed up in that many of the line items produced are not patch
files. Perhaps that's why the auto-keep-in-sync stuff doesn't appear
to be working any longer.

What I remember is that every day there was a cron job that:

1) Checks to ensure that any patch called for in BLFS svn actually
exists in the LFS repo. Mail was sent out to BLFS-BOOK if a patch
couldn't be located in the SVN repo.

2) Checks to ensure that any patch that has become obsolete in
BLFS SVN is no longer in the BLFS repo (repo is deleleted and
recreated from only active BLFS SVN patches).

Anyone who knows care to fill in the missing pieces here?

-- 
Randy

rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
11:02:00 up 14 days, 11:16, 1 user, load average: 0.93, 0.36, 0.13
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to