Maintenance script: Created page with " === Description of the initial problem === It might happen that a ncm-component has been patched in Github, but that the RPM have not been re-created in the yum.quattor.org ..."

2015-08-26T12:28:31Z

Created page with " === Description of the initial problem === It might happen that a ncm-component has been patched in Github, but that the RPM have not been re-created in the yum.quattor.org ..."

New page

=== Description of the initial problem ===
It might happen that a ncm-component has been patched in Github, but that the RPM have not been re-created in the yum.quattor.org repository. The solution is then to create your own "homebrew" RPM from the correct code and to put this RPM in a local repo, and to bring the necessary changes in the PAN templates to install the homebrew RPM from the local repo.
=== Git clone of a tag ===
The general procedure is the following :
<pre>
git clone <repo-address>
git tag -l
git checkout <tag-name>
git branch -D master
git checkout -b master
</pre>
=== Use of maven to build an RPM ===
*First set up your environment :
**Your must first make sure that Java from Oracle is installed and is the default.
**Let's say that maven 3.1.1 has been installed in /root/maven/apache-maven-3.1.1 (the installation is explained here : http://maven.apache.org/download.cgi#Installation).
**Set your env. var. to the correct values :
<pre>
export M2_HOME=/root/maven/apache-maven-3.1.1
export M2=$M2_HOME/bin
export PATH=$M2:$PATH
export JAVA_HOME=/usr/java/jdk1.6.0_04
export PATH=$JAVA_HOME:$PATH
</pre>
*Go into the directory of your component and edit the pom.xml file. Modify the value of the version tag. For example, if the version is 13.1.1, then append '-iihe' to it, this way the name of your homebrew RPM will be slightly different from the one that is in the official repo.
*Run the maven command :
<pre>
mvn rpm:rpm
</pre>

{{TracNotice|{{PAGENAME}}}}

GenerateRPMFromATagInGithub - Revision history

Maintenance script: Created page with " === Description of the initial problem === It might happen that a ncm-component has been patched in Github, but that the RPM have not been re-created in the yum.quattor.org ..."