Changes

From SME Server
Jump to navigationJump to search
Line 41: Line 41:  
  # usage: mock -r <mock_config> --rebuild /path/to/SRPM e.g.
 
  # usage: mock -r <mock_config> --rebuild /path/to/SRPM e.g.
 
  $ mock -r $CONFIG --rebuild ~/rpmbuild/SRPMS/e-smith-runit-2.4.0-1.el6.sme.src.rpm
 
  $ mock -r $CONFIG --rebuild ~/rpmbuild/SRPMS/e-smith-runit-2.4.0-1.el6.sme.src.rpm
If the build succeeds, it drops your packages into the /var/lib/mock/$CONFIG/result directory:
+
 
 +
If the build succeeds, it drops your packages into the /var/lib/mock/$CONFIG/result directory. If it fails, you can check mock output, the *.log files above for more info, and/or rerun mock with the -v flag for more verbose messaging.
    
  ls -1 /var/lib/mock/smeserver-9-x86_64/result
 
  ls -1 /var/lib/mock/smeserver-9-x86_64/result
Line 49: Line 50:  
  root.log
 
  root.log
 
  state.log
 
  state.log
If it fails, you can check mock output, the *.log files above for more info, and/or rerun mock with the -v flag for more verbose messaging.
+
 
 +
Normally you make builds from the working directory of the module you are working on, eg ~/rpms/e-smith-runit/sme9:
 +
# Build the given module within the chroot environment
 +
$ cd ~/rpms/e-smith-runit/sme9
 +
$ make mockbuild
 +
 
 +
It will determine if this is for SME Server 9 or 8, and the package to build, based on which directory that you are in. The results are put under that directory.
 +
 
 +
ls -1 ~/rpms/e-smith-runit/sme9/e-smith-runit-2_4_0-2_el6_sme/
 +
build.log
 +
e-smith-runit-2.4.0-2.el6.sme.noarch.rpm
 +
e-smith-runit-2.4.0-2.el6.sme.src.rpm
 +
root.log
 +
state.log
 +
 
    
Notes:
 
Notes:

Navigation menu