Changes

Jump to navigation Jump to search

SME Server:Documentation:Developers Manual:Chapter13 (view source)

Revision as of 13:18, 27 April 2008

478 bytes removed ,  13:18, 27 April 2008
→‎Building an RPM: fix wiki coding,
Line 104: Line 104:  
This section describes the process for building an RPM - step by step.
 
This section describes the process for building an RPM - step by step.
   −
# Choose a name and version number for your package. We are going to package the complete loggerdemo example and will use <var class="LITERAL">loggerdemo</var> and <var class="LITERAL">1.0.0</var> as the name and version number.
+
Choose a name and version number for your package. We are going to package the complete loggerdemo example and will use <var class="LITERAL">loggerdemo</var> and <var class="LITERAL">1.0.0</var> as the name and version number.
−
# Collect all of the files which have been created in the previous sections into the <tt class="FILENAME">/tmp/</tt> directory. There is one additional file <tt class="FILENAME">createlinks</tt> which looks like this: <nowiki>#!/usr/bin/perl -w
+
 
 +
Collect all of the files which have been created in the previous sections into the <tt class="FILENAME">/tmp/</tt> directory. There is one additional file <tt class="FILENAME">createlinks</tt> which looks like this:  
 +
 
 +
#!/usr/bin/perl -w
 
   
 
   
 
  use esmith::Build::CreateLinks qw(:all);
 
  use esmith::Build::CreateLinks qw(:all);
Line 114: Line 117:  
  panel_link("loggerdemo", $panel);
 
  panel_link("loggerdemo", $panel);
 
   
 
   
−
</nowiki>
+
Create the directory hierarchy required for building the RPM. This is very close to the hierarchy on the installed system.  
−
# Create the directory hierarchy required for building the RPM. This is very close to the hierarchy on the installed system. <nowiki># Change to the SOURCES directory
+
 
 +
# Change to the SOURCES directory
 
  cd ~/rpms/SOURCES
 
  cd ~/rpms/SOURCES
 
   
 
   
Line 142: Line 146:  
   
 
   
 
  # The createlinks auxiliary file
 
  # The createlinks auxiliary file
−
  cp -p /tmp/createlinks .</nowiki>Your directory structure should now look like this: [gordonr@sevendev1 loggerdemo-1.0.0]$ find . -type f
+
  cp -p /tmp/createlinks .
 +
 
 +
Your directory structure should now look like this:  
 +
 
 +
[gordonr@sevendev1 loggerdemo-1.0.0]$ find . -type f
 
  ./root/etc/e-smith/templates/etc/crontab/25templatedemo
 
  ./root/etc/e-smith/templates/etc/crontab/25templatedemo
 
  ./root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/loggerdemo
 
  ./root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/loggerdemo
Line 148: Line 156:  
  ./root/usr/lib/perl5/site_perl/esmith/FormMagick/Panel/loggerdemo.pm
 
  ./root/usr/lib/perl5/site_perl/esmith/FormMagick/Panel/loggerdemo.pm
 
  ./createlinks
 
  ./createlinks
−
# Package the directory into a tarball: cd ~/rpms/SOURCES
+
 
 +
Package the directory into a tarball: cd ~/rpms/SOURCES
 
  tar zcvf loggerdemo-1.0.0.tar.gz loggerdemo-1.0.0
 
  tar zcvf loggerdemo-1.0.0.tar.gz loggerdemo-1.0.0
−
# Create the RPM specification "SPEC" file <tt class="FILENAME">~/rpms/SPECS/loggerdemo.spec</tt> which looks like this: <nowiki>
+
 
−
%define name loggerdemo
+
Create the RPM specification "SPEC" file <tt class="FILENAME">~/rpms/SPECS/loggerdemo.spec</tt> which looks like this:  
 +
 
 +
%define name loggerdemo
 
  %define version 1.0.0
 
  %define version 1.0.0
 
  %define release 01
 
  %define release 01
Line 180: Line 191:  
  perl createlinks
 
  perl createlinks
 
   
 
   
 +
## NEW ADVICE, DB fragments should be created as files
 
  DEFAULTS=root/etc/e-smith/db/configuration/defaults/loggerdemo
 
  DEFAULTS=root/etc/e-smith/db/configuration/defaults/loggerdemo
 
  mkdir -p $DEFAULTS
 
  mkdir -p $DEFAULTS
Line 186: Line 198:  
  echo "enabled"  > $DEFAULTS/status
 
  echo "enabled"  > $DEFAULTS/status
 
  echo "10"      > $DEFAULTS/Interval
 
  echo "10"      > $DEFAULTS/Interval
−
   
   
 
   
 
  %install
 
  %install
Line 198: Line 209:  
   
 
   
 
  %post
 
  %post
−
/etc/e-smith/events/actions/initialize-default-databases
  −
/etc/e-smith/events/actions/navigation-conf
   
  /sbin/e-smith/expand-template /etc/crontab
 
  /sbin/e-smith/expand-template /etc/crontab
 
  true
 
  true
Line 210: Line 219:  
  %defattr(-,root,root)
 
  %defattr(-,root,root)
 
   
 
   
−
</nowiki>Note the <var class="LITERAL">%post</var> (post-installation) and <var class="LITERAL">%postun</var> (post-uninstallation) statements which expand the <tt class="FILENAME">/etc/crontab</tt> template after installing or uninstalling the RPM.
+
 
−
# Check that your RPM will build OK with "build prepare": cd ~/rpms/SPECS
+
Note the <var class="LITERAL">%post</var> (post-installation) and <var class="LITERAL">%postun</var> (post-uninstallation) statements which expand the <tt class="FILENAME">/etc/crontab</tt> template after installing or uninstalling the RPM.
−
  rpmbuild -bp loggerdemo.specThe last line of output should be <var class="LITERAL">+ exit 0</var> if rpmbuild is successful.
+
 
−
# Run the '''rpmbuild''' command again to actually create your RPM with the "build all" options: rpmbuild -ba loggerdemo.specIf everything was successful, the last line of output should again be <var class="LITERAL">+ exit 0</var>.
+
Check that your RPM will build OK with "build prepare":  
−
# The RPMs should have been generated and put into <tt class="FILENAME">~/rpms/RPMS/noarch/</tt> as this program can run equally well on any platform. A source RPM should also exist in <tt class="FILENAME">~/rpms/SRPMS/</tt>.
+
cd ~/rpms/SPECS
−
# Test your RPM by installing it on an SME Server test box.<div class="NOTE"><blockquote class="NOTE">'''Note: '''RPMs need to be installed as <var class="LITERAL">root</var>, but you should not log in as the root user. Instead, you should create a normal user and provide them with 'root' privileges via the '''sudo''' command. To provide full <span class="emphasis">''sudo''</span> rights to the user <var class="LITERAL">joe</var>, use the '''su - -c /usr/sbin/visudo''' and add the following line to the end of the file: joe    ALL=(ALL) ALLYou can then use the '''sudo''' to run commands as <var class="LITERAL">root</var> when required. You will be prompted for your password (not the root password) which ensures that someone else isn't using your terminal.</blockquote></div> [joe@sevendev1 SPECS]$ sudo rpm -Uvh \
+
  rpmbuild -bp loggerdemo.spec
−
    ~/rpms/RPMS/noarch/loggerdemo-1.0.0-01.noarch.rpm
+
 +
The last line of output should be <var class="LITERAL">+ exit 0</var> if rpmbuild is successful.
 +
 
 +
Run the '''rpmbuild''' command again to actually create your RPM with the "build all" options:
 +
rpmbuild -ba loggerdemo.spec
 +
 
 +
If everything was successful, the last line of output should again be <var class="LITERAL">+ exit 0</var>.
 +
 
 +
The RPMs should have been generated and put into <tt class="FILENAME">~/rpms/RPMS/noarch/</tt> as this program can run equally well on any platform. A source RPM should also exist in <tt class="FILENAME">~/rpms/SRPMS/</tt>.
 +
 
 +
Test your RPM by installing it on an SME Server test box.
 +
 
 +
<div class="NOTE"><blockquote class="NOTE">'''Note: '''RPMs need to be installed as <var class="LITERAL">root</var>, but you should not log in as the root user. Instead, you should create a normal user and provide them with 'root' privileges via the '''sudo''' command. To provide full <span class="emphasis">''sudo''</span> rights to the user <var class="LITERAL">joe</var>, use the '''su - -c /usr/sbin/visudo''' and add the following line to the end of the file: joe    ALL=(ALL) ALLYou can then use the '''sudo''' to run commands as <var class="LITERAL">root</var> when required. You will be prompted for your password (not the root password) which ensures that someone else isn't using your terminal.</blockquote></div>  
 +
 
 +
sudo yum localinstall  ~/rpms/RPMS/noarch/loggerdemo-1.0.0-01.noarch.rpm
 
  Preparing...                ########################################### [100%]
 
  Preparing...                ########################################### [100%]
 
     1:loggerdemo            ########################################### [100%]
 
     1:loggerdemo            ########################################### [100%]
Line 230: Line 253:  
  Migrating existing database backups
 
  Migrating existing database backups
 
  Migrating existing database yum_available
 
  Migrating existing database yum_available
−
  Migrating existing database domains<div class="NOTE"><blockquote class="NOTE">'''Note: '''In almost all instances you should use the <var class="LITERAL">-U</var> (upgrade) option to rpm instead of the <var class="LITERAL">-i</var> (install) option. The <var class="LITERAL">-i</var> option should be reserved for special operations, such as installing kernels.</blockquote></div>The customization should be fully installed, and the <tt class="FILENAME">/etc/crontab</tt> file should show the customization. Then remove the customization: <nowiki># remove the RPM
+
  Migrating existing database domains
−
  sudo rpm -e loggerdemo</nowiki>The customization should be completely gone, and the <tt class="FILENAME">/etc/crontab</tt> file should look the way it did before.
+
 
 +
The customization should be fully installed, and the <tt class="FILENAME">/etc/crontab</tt> file should show the customization.  
 +
 
 +
Then remove the customization:  
 +
  sudo rpm -e loggerdemo
 +
 
 +
The customization should be completely gone, and the <tt class="FILENAME">/etc/crontab</tt> file should look the way it did before.
    
<div class="SECT2">
 
<div class="SECT2">
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/9493"

Navigation menu