[RFC] LFS profile testing

Thomas Pegg thomasp at linuxfromscratch.org
Sun Jun 20 14:58:08 PDT 2004

On Sun, 2004-06-20 at 01:02, Kevin P. Fleming wrote:
> The profile maintenance team needs to come up with some method and/or 
> procedure for testing profile changes before we release them. Tonight I 
> found two problems in the LFS-5.1.1-2 profile (already corrected and 
> released as LFS-5.1.1-3):
> - the config_tarball package.ent file was using the wrong name for the 
> expect patch
> - the config_tarball package.ent file did not have entities for nALFS 
> and libxml2 (this one is my fault, I was the one who added them to 
> config_seperate)
> I'd like to see some procedure set up for one (or more) of the profile 
> team to actually run through a complete build, both "seperate" and 
> "tarball" mode, before we say that a new LFS profile is ready for 
> release. I don't think this is needed for patch-level updates (-2, -3, 
> etc.) as long as we are diligent in locally testing our changes, but 
> certainly when we are close to converting the HEAD profile into a 
> released version we should get successful build confirmations from as 
> many team members as possible before releasing the profile.

I usually test most changes before I commit them, unless it's something
really simple, then I don't, but otherwise I'll run a full build before
I commit anything. One thing I've always done before I tar up the
profiles, is go through each section of the book and look at the profile
and see if things match up as they should, sort of an audit I guess you
could call it.
LFS User : 4729 
Linux User : 298329 
warpcore - 16:42:34 up 3:16, 1 user, load average: 0.07, 0.13, 0.09
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxfromscratch.org/pipermail/alfs-discuss/attachments/20040620/338f712b/attachment.sig>

More information about the alfs-discuss mailing list