CVS: src/si/docs README.phase4,NONE,1.1 README,1.10,1.11 package_list,1.25,NONE

Update of /cvsroot/lsb/src/si/docs
In directory sc8-pr-cvs1:/tmp/cvs-serv14585

Modified Files:
	README 
Added Files:
	README.phase4 
Removed Files:
	package_list 
Log Message:
Add some notes on phase4, and a separate README.  Remove package_list -
not used any longer.


--- NEW FILE ---
Phase4 is actually three distinct pieces:

phase4a == add-ons for chroot environment (lsbsi-test)
phase4b == add-ons for bootable environment (lsbsi-boot)
phase4c == add-ons for user-mode-linux environment (lsbsi-uml)

These are built independently of each other, although they share a number
of common elements; they're also built independently of phase 3.

The latter condition causes a little bit of extra work: none of the phase4
bits have a complete environment, each is instead designed to layer
on top of phase 3 to produce a target.  Thus, in the system-config and
finalize phases, where we'd normally chroot and configure, we now have to
have phase-specific files that write to the correct location.  Thus, for
example, we have three nearly identical system-config/inetd4x.xml files,
where only the <base> element differs.  If we were able to chroot, the
three phases could share one xml file that just wrote to /etc/inetd.conf
inside that chroot.

The upside of this is that if it turns out something needs to be
different in the phases, the mechanism is already there to support
that, but the downside is that if you find a bug you may have to
remember to fix it in three places.

Index: README
===================================================================
RCS file: /cvsroot/lsb/src/si/docs/README,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** README	15 Jan 2003 22:00:15 -0000	1.10
--- README	28 Jan 2003 16:15:38 -0000	1.11
***************
*** 170,179 ****
  and not fix or tweak anything this is the command for you.
  
! LSB.phase4.xml builds three add-on packages that can be layered on top of
! a finished sample implementation to tune it for particular uses.  These are
! internally described as sub-phases 4a, 4b and 4c.  They support running the
! LSB runtime test suite; building a bootable system; and running a system
! that can be run in user-mode Linux, respectively.  LSB.xml does *not* run
! phase4 at this writing, it must be invoked separately.
  
  make targets support each of the above builds, and can be easily identified
--- 170,180 ----
  and not fix or tweak anything this is the command for you.
  
! LSB.phase4.xml builds three add-on packages that can be layered on
! top of a finished sample implementation to tune it for particular uses.
! These are internally described as sub-phases 4a, 4b and 4c.  They support
! running the LSB runtime test suite in a chroot environment; building
! a bootable system; and running a system that can be run in user-mode
! Linux, respectively.  LSB.xml does *not* run phase4 at this writing,
! it must be invoked separately.
  
  make targets support each of the above builds, and can be easily identified
***************
*** 275,285 ****
  it refers to one of phase3's components.
  
! phase4 follows the same scheme as phase3, in that it uses phase2, and builds
! completely independently.  phase4 does not do anything with a previously
! built phase3.  &LFS-phase4-install; should be used with any directory
! or file name to ensure it refers to the correct component; packages have
! indpendent entries in the system file for each of the three subphases, as in
! &phase4c-build-e2fsprogs; &phase4c-build-e2fsprogs; &phase4c-build-e2fsprogs;
  
  
  =============================================================================
--- 276,289 ----
  it refers to one of phase3's components.
  
! phase4 follows the same scheme as phase3, in that it uses phase2, and
! builds completely independently - it does not use a previously built
! phase3. In fact, each of the three phase4 bits builds independently of
! the others. The entity &LFS-phase4-install; should be used with any
! directory or file name to ensure it refers to the correct component;
! packages have indpendent entries in the system file for each of the three
! subphases, as in &phase4c-build-e2fsprogs; &phase4c-build-e2fsprogs;
! &phase4c-build-e2fsprogs;
  
+ See also README.phase4 for additional notes on phase4.
  
  =============================================================================