Difference between revisions of "Build The Manifest"

From NST Wiki
Jump to navigationJump to search
Line 2: Line 2:
  
 
* Use the ''make manifest HOST=IP'' to generate the current manifest.
 
* Use the ''make manifest HOST=IP'' to generate the current manifest.
 +
 +
* Create the file ''include/manifest/release-RELEASE-SVNID.xml'' where ''RELEASE'' is the NST release (like: 2.13.0) and ''SVNID'' is ''one more'' than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 2065, then use 2066 as the ''SVNID''.
  
 
* Commit the updated manifest file.
 
* Commit the updated manifest file.
  
 
* Force the ''nstwui'', ''nstmenu'' and ''nstweb'' packages to be rebuilt.
 
* Force the ''nstwui'', ''nstmenu'' and ''nstweb'' packages to be rebuilt.
 +
 +
Here is an example of what these steps might look like:
  
 
  [root@nst-dev-32 repo]# make manifest HOST=nst-probe
 
  [root@nst-dev-32 repo]# make manifest HOST=nst-probe
Line 11: Line 15:
 
  ... Output and re-generation of:
 
  ... Output and re-generation of:
 
     include/manifest/current.xml ...
 
     include/manifest/current.xml ...
 +
 +
[root@f13-32 repo]# svn info
 +
Path: .
 +
URL: https://nst.svn.sourceforge.net/svnroot/nst/trunk
 +
Repository Root: https://nst.svn.sourceforge.net/svnroot/nst
 +
Repository UUID: c9574408-7c70-44fe-bb37-9fe24d5f8586
 +
Revision: 2065
 +
Node Kind: directory
 +
Schedule: normal
 +
Last Changed Author: pblankenbaker
 +
Last Changed Rev: 2065
 +
Last Changed Date: 2011-05-09 16:55:15 -0400 (Mon, 09 May 2011)
 
   
 
   
  [root@nst-dev-32 repo]# cp include/manifest/current.xml include/manifest/release-RELEASE.xml
+
  [root@nst-dev-32 repo]# cp include/manifest/current.xml include/manifest/release-2.13.0-2066.xml
 
  [root@nst-dev-32 repo]# svn add include/manifest/release-RELEASE.xml
 
  [root@nst-dev-32 repo]# svn add include/manifest/release-RELEASE.xml
 
  [root@nst-dev-32 repo]# svn commit
 
  [root@nst-dev-32 repo]# svn commit

Revision as of 17:17, 9 May 2011

  • Boot the current build of the NST ISO image.
  • Use the make manifest HOST=IP to generate the current manifest.
  • Create the file include/manifest/release-RELEASE-SVNID.xml where RELEASE is the NST release (like: 2.13.0) and SVNID is one more than the current revision number reported by Subversion (since our next commit will cause this number to bump up by 1). For example, if the revision number reported is 2065, then use 2066 as the SVNID.
  • Commit the updated manifest file.
  • Force the nstwui, nstmenu and nstweb packages to be rebuilt.

Here is an example of what these steps might look like:

[root@nst-dev-32 repo]# make manifest HOST=nst-probe

... Output and re-generation of:
    include/manifest/current.xml ...
[root@f13-32 repo]# svn info
Path: .
URL: https://nst.svn.sourceforge.net/svnroot/nst/trunk
Repository Root: https://nst.svn.sourceforge.net/svnroot/nst
Repository UUID: c9574408-7c70-44fe-bb37-9fe24d5f8586
Revision: 2065
Node Kind: directory
Schedule: normal
Last Changed Author: pblankenbaker
Last Changed Rev: 2065
Last Changed Date: 2011-05-09 16:55:15 -0400 (Mon, 09 May 2011)

[root@nst-dev-32 repo]# cp include/manifest/current.xml include/manifest/release-2.13.0-2066.xml
[root@nst-dev-32 repo]# svn add include/manifest/release-RELEASE.xml
[root@nst-dev-32 repo]# svn commit

... Output from the commit ...

[root@nst-dev-32 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove

... This remove will force them to be rebuilt ...

[root@nst-dev-32 repo]#

***Note: One may need to edit the current release file: "include/manifest/current.xml" prior to copying it for misbehaved characters.