Difference between revisions of "Build The Manifest"

From NST Wiki
Jump to navigationJump to search
Line 11: Line 11:
 
Here is an example of what these steps might look like:
 
Here is an example of what these steps might look like:
  
  [root@nst-dev-32 repo]# make manifest HOST=nst-probe
+
  [root@dev18-32 repo]# make manifest HOST=nst-probe
 
   
 
   
 
  ... Output and re-generation of:
 
  ... Output and re-generation of:
 
     include/manifest/current.xml ...
 
     include/manifest/current.xml ...
 
   
 
   
  [root@f13-32 repo]# xmllint include/manifest/current.xml > /dev/null
+
  [root@dev18-32 repo]# xmllint include/manifest/current.xml > /dev/null
  [root@f13-32 repo]# grep '%' include/manifest/current.xml
+
  [root@dev18-32 repo]# grep '%' include/manifest/current.xml
  [root@f13-32 repo]# svn info
+
  [root@dev18-32 repo]# svn info
 
  Path: .
 
  Path: .
  URL: https://nst.svn.sourceforge.net/svnroot/nst/trunk
+
Working Copy Root Path: /root/repo
  Repository Root: https://nst.svn.sourceforge.net/svnroot/nst
+
  URL: https://svn.code.sf.net/p/nst/code/repo
  Repository UUID: c9574408-7c70-44fe-bb37-9fe24d5f8586
+
  Repository Root: https://svn.code.sf.net/p/nst/code
  Revision: 2511
+
  Repository UUID: b5e161f0-cc72-4f2a-9017-da5bd5071a9c
 +
  Revision: 4504
 
  Node Kind: directory
 
  Node Kind: directory
 
  Schedule: normal
 
  Schedule: normal
  Last Changed Author: pblankenbaker
+
  Last Changed Author: rwhalb
  Last Changed Rev: 2511
+
  Last Changed Rev: 4504
  Last Changed Date: 2011-08-09 16:55:15 -0400 (Tue, 09 Aug 2011)
+
  Last Changed Date: 2013-04-12 15:13:52 -0400 (Fri, 12 Apr 2013)
 
   
 
   
  [root@nst-dev-32 repo]# cp include/manifest/current.xml include/manifest/release-2.15.0-2512.xml
+
  [root@dev18-32 repo]# cp include/manifest/current.xml include/manifest/release-18-4505.xml
  [root@nst-dev-32 repo]# svn add include/manifest/release-2.15.0-2512.xml
+
  [root@dev18-32 repo]# svn add include/manifest/release-18-4505.xml
  [root@nst-dev-32 repo]# svn commit
+
  [root@dev18-32 repo]# svn commit -m "Updated manifest for upcoming release"
 
   
 
   
 
  ... Output from the commit ...
 
  ... Output from the commit ...
 
   
 
   
  [root@nst-dev-32 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove
+
  [root@dev18-32 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove
 
   
 
   
 
  ... This remove will force them to be rebuilt ...
 
  ... This remove will force them to be rebuilt ...
 
   
 
   
  [root@nst-dev-32 repo]#
+
  [root@dev18-32 repo]#
  
 
'''***Note1:''' One may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' search for the ''%'' character will detect any issues.
 
'''***Note1:''' One may need to ''edit'' the current release file: "'''include/manifest/current.xml'''" prior to copying it for misbehaved characters. Hopefully the ''xmllint'' and ''grep'' search for the ''%'' character will detect any issues.
  
'''***Note2:''' You will likely need to update the ''html/welcome.html'' page with the next SVN revision number (''2512'' in this example).
+
'''***Note2:''' You will likely need to update the ''html/welcome.html'' page with the next SVN revision number (''4505'' in this example).
  
 
'''***Note3:''' 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:
 
'''***Note3:''' 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
+
  [root@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove

Revision as of 16:54, 12 April 2013

  • 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@dev18-32 repo]# make manifest HOST=nst-probe

... Output and re-generation of:
    include/manifest/current.xml ...

[root@dev18-32 repo]# xmllint include/manifest/current.xml > /dev/null
[root@dev18-32 repo]# grep '%' include/manifest/current.xml
[root@dev18-32 repo]# svn info
Path: .
Working Copy Root Path: /root/repo
URL: https://svn.code.sf.net/p/nst/code/repo
Repository Root: https://svn.code.sf.net/p/nst/code
Repository UUID: b5e161f0-cc72-4f2a-9017-da5bd5071a9c
Revision: 4504
Node Kind: directory
Schedule: normal
Last Changed Author: rwhalb
Last Changed Rev: 4504
Last Changed Date: 2013-04-12 15:13:52 -0400 (Fri, 12 Apr 2013)

[root@dev18-32 repo]# cp include/manifest/current.xml include/manifest/release-18-4505.xml
[root@dev18-32 repo]# svn add include/manifest/release-18-4505.xml
[root@dev18-32 repo]# svn commit -m "Updated manifest for upcoming release"

... Output from the commit ...

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

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

[root@dev18-32 repo]#

***Note1: One may need to edit the current release file: "include/manifest/current.xml" prior to copying it for misbehaved characters. Hopefully the xmllint and grep search for the % character will detect any issues.

***Note2: You will likely need to update the html/welcome.html page with the next SVN revision number (4505 in this example).

***Note3: 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@dev18-64 repo]# make -C yum nstwui-remove nstweb-remove nstmenu-remove