From: S. Skole
                                                           Date: 2000-02-29


             VLT-SW-FEB2000 - RELEASE NOTES FOR pkgin
             =================================================

Version:
   
   pkgin 1.28

Document:

   VLT-MAN-ESO-17240-1913

New Features:

   By the aid of the keywords INSTALL.MODULEi.CPU and
   INSTALL.MODULE.CPU it is possible to generate LCU code
   for various processors.

Fixed Problems:

   The following SPRs have been closed since the OCT99 Release.

   VLTSW990491
   VLTSW20000002
   VLTSW20000030
   VLTSW20000025
   VLTSW20000026
   VLTSW20000053
   VLTSW20000049
   VLTSW20000051
   VLTSW20000046
   VLTSW20000056

Known Problems:

  The SPR VLTSW990343 addresses a bug of vccEnvCreate,
  which makes it impossible to create an environment off-line,
  unless the destination is $VLTDATA/ENVIRONMENTS.
  Since pkgin uses the vccEnv utilities, and uses another destination
  as the one specified above when building off-line, pkginBuild must be
  invoked on the target machine. Though, this requirement only applies to
  packages containing environments.

  The SPR VLTSW20000025 addresses problems with the use of old keywords
  for detector installations. Detector installation is a new feature
  of pkgin, but it is only partly implemented, and will not be
  available until OCT2000. Meanwhile the already implemented Tcl code
  has been commented out. The new keywords for this feature are already
  in the dictionary, but it has no effect using them.
	    
  When pkgin creates and starts LCU environments, it scans and possibly 
  modifies the boot files .bootChange.start, .bootChange.stop and bootScript. 
  By this scanning some empty lines are unintentionally added to the end of 
  the above mentioned files, and they will cause the vccEnv tools to hang 
  when trying to start the environment. Meanwhile the bug has been fixed, 
  and it is recommended to upgrade to pkgin version 1.30 or higher, when 
  the package contains LCU environments. 

Compatibility:

  pkgin should be backward compatible with the OCT99 release.
  Therefore, if any problems regarding this issue arise, they are 
  considered bugs and should be reported.


                                ___oOo___