If you don't use the Distribution Constructor or
distro_const(1M), feel free to discard this message
now.

With the putback of changeset 958:552c24933bed in
build 156 of the slim_source gate, distro_const(1M) has been completely re-written to take advantage of the new Install infrastructure.

What has changed?
-----------------

DC has been re-written to use the CUD (Caiman Unified Design) components. It is now purely a python application.
The format of the DC manifests has changed and they
are now in the DTD XML format.

In addition to this, a number of outstanding bugs and RFEs[1]
have been fixed that should make the user experience
considerably better.

How do the changes impact me?
-----------------------------

The following are the user visible impacts of this change:

a) '-R' option (resume at next unexecuted step) to
   distro_const(1M) has been removed due to lack of use.

b) DC manifests have been renamed to:
   dc_livecd.xml
   dc_ai_x86.xml
   dc_ai_sparc.xml
   dc_text_x86.xml
   dc_text_sparc.xml

   The manifests are now in the DTD format and they are laid
   out significantly differently than before.

   As a general note, you should only need to edit the
   target section of the manifest to specify the location
   of the build area, and the software section to specify the
   package repository and package list.

c) Existing finalizer scripts are not compatible with the
   revised Distribution Constructor. Custom extensions to DC
   are easily accomodated by using the custom-script checkpoint,
   which is documented here:

   http://hub.opensolaris.org/bin/view/Project+caiman/%0D%0AInstructions

d) As was the case with the old DC, this revision of DC requires
   that the Solaris build version that you're running on your
   build machine must be the same as that of the media
   you're building. For instance, if you are intending to
   build media based on 151, your build machine must be
   running 151.

   While build version mismatch will not prevent DC
   from running, it is *strongly* discouraged as it can often
   lead to unpredictable results that are hard to diagnose.

Please redirect all your questions to [email protected]

[1] 7000990 The logging module needs a transfer_log method for the FileHandler
class
16706 DC Schema should be reworked
15716 DC should check return code of commands and fail the build if command
fails
15480 Make hostname for images configurable parameter in DC manifests
15214 DC should "lock" the directory/zfs dataset during execution
14972 distro construction should not use tools/libraries from the new image
14433 Need to remove mkrepo when Early Manifest Import functionality is
available
10750 setting up of the grub menu in DC could be more modular
8702 Update slimcd_pre_bootroot_pkg_image_mod to use the force option to
regenerate the caches
6794 DC should provide a way to label output image separate from distribution
name
6336 im-pop step should be broken up
4392 Distro constructor should provide better interface to specify compression
3814 DC logging should begin immediately when the app is invoked
3553 distro_const command creates zfs datasets before validating the cli args
2361 Need more elegant way to run GNOME services in DC
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to