Build The Manifest

• 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.15.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 2511, then use 2512 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: 2511
Node Kind: directory
Schedule: normal
Last Changed Author: pblankenbaker
Last Changed Rev: 2511
Last Changed Date: 2011-08-09 16:55:15 -0400 (Tue, 09 Aug 2011)

[root@nst-dev-32 repo]# cp include/manifest/current.xml include/manifest/release-2.15.0-2512.xml
[root@nst-dev-32 repo]# svn add include/manifest/release-2.15.0-2512.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]#

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

***Note2: You only need to update the manifest on the 32 bit development machine. On the 64 bit machine you will just run svn update to get the newly committed manifest. Also, it won't hurt to run the following on the 64 bit machine:

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