5,576
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
# This is an example spec file for SME Server rpm building.
# This is an example spec file for SME Server rpm building.
# The Summary line is a single line description of the module.
# The Summary line is a single line description of the module.
=== Summary: PackageName for SME Server ===
==== Summary: PackageName for SME Server ====
# anything starting with a % sign is a command that is interpreted by
# anything starting with a % sign is a command that is interpreted by
# name is. If we were doing the SME Server specific bits in a separate RPM,
# name is. If we were doing the SME Server specific bits in a separate RPM,
# we'd probably call it smeserver-PackageName
# we'd probably call it smeserver-PackageName
=== %define name smeserver-PackageName ===
==== %define name smeserver-PackageName ====
# now you'll see how we refer to a value we've set previously. If we
# now you'll see how we refer to a value we've set previously. If we
# did "%define foo bar" we can use "%{foo}" to insert "bar" in that
# did "%define foo bar" we can use "%{foo}" to insert "bar" in that
# place.
# place.
=== Name: %{name} ===
==== Name: %{name} ====
# and some more of the same with version and release numbers.
# and some more of the same with version and release numbers.
=== %define version 1.0.0 ===
==== %define version 1.0.0 ====
=== %define release 02 ===
==== %define release 02 ====
=== Version: %{version} ===
==== Version: %{version} ====
=== Release: %{release} ===
==== Release: %{release} ====
# The copyright should be "GPL" for any contrib module you hope to
# The copyright should be "GPL" for any contrib module you hope to
# make available for other SME Server users
# make available for other SME Server users
=== Copyright: GPL ===
==== Copyright: GPL ====
# The Group should indicate the type of application you're packaging.
# The Group should indicate the type of application you're packaging.
# You can find a list of groups by looking at your current installed rpm
# You can find a list of groups by looking at your current installed rpm
# package documentation: /usr/share/doc/rpm-x.x.x/GROUPS
# package documentation: /usr/share/doc/rpm-x.x.x/GROUPS
=== Group: Networking/Daemons ===
==== Group: Networking/Daemons ====
# This is the name of the source file to use. Notice how we generate it
# This is the name of the source file to use. Notice how we generate it
# based on the name and version we set earlier?
# based on the name and version we set earlier?
=== Source: %{name}-%{version}.tar.gz ===
==== Source: %{name}-%{version}.tar.gz ====
# If you are using patch files, put some statements to define the
# If you are using patch files, put some statements to define the
# where 'identity' references who you are, work for or represent.
# where 'identity' references who you are, work for or represent.
# This could be your abreviated companyname or personal initials.
# This could be your abreviated companyname or personal initials.
=== Patch0: smeserver-PackageName-1.0.0-02.dtm_patch ===
==== Patch0: smeserver-PackageName-1.0.0-02.dtm_patch ====
# The Packager is the name and email address of the person who packaged
# The Packager is the name and email address of the person who packaged
# this software for SME Server, who may be a different person to the one
# this software for SME Server, who may be a different person to the one
# who originally wrote it.
# who originally wrote it.
=== Packager: Fred Foonly <foonly@example.com> ===
==== Packager: Fred Foonly <foonly@example.com> ====
# Where to do the work of building the RPMs. This should be a temporary
# Where to do the work of building the RPMs. This should be a temporary
# directory unique to this package, hence we use the name, version and
# directory unique to this package, hence we use the name, version and
# release values we set earlier to make up the directory name
# release values we set earlier to make up the directory name
=== BuildRoot: /var/tmp/%{name}-%{version}-%{release}-buildroot ===
==== BuildRoot: /var/tmp/%{name}-%{version}-%{release}-buildroot ====
# What architectures do we want to build this for? Use "i386" if your
# What architectures do we want to build this for? Use "i386" if your
# Perl and many web applications. Most SME Server management RPMs should
# Perl and many web applications. Most SME Server management RPMs should
# be "noarch"
# be "noarch"
=== BuildArchitectures: noarch ===
==== BuildArchitectures: noarch ====
# What software is required to build the RPM? This lets the RPM program
# What software is required to build the RPM? This lets the RPM program
# software requires the package smeserver-devtools version 0.1-3 or higher
# software requires the package smeserver-devtools version 0.1-3 or higher
# to run correctly.
# to run correctly.
=== BuildRequires: smeserver-devtools >= 0.1-3 ===
==== BuildRequires: smeserver-devtools >= 0.1-3 ====
# What software is required for the RPM to run correctly once it's
# What software is required for the RPM to run correctly once it's
# installed on a system? This has the same format as BuildRequires
# installed on a system? This has the same format as BuildRequires
=== Requires: PackageName >= 2.2 ===
==== Requires: PackageName >= 2.2 ====
# typically, smeserver-PackageName will require PackageName, so you have to have
# typically, smeserver-PackageName will require PackageName, so you have to have
# What software is required for the RPM to run correctly once it's
# What software is required for the RPM to run correctly once it's
# installed on a system? This has the same format as BuildRequires
# installed on a system? This has the same format as BuildRequires
=== Requires: PackageName >= 2.2 ===
==== Requires: PackageName >= 2.2 ====
# What software is obsolete and will be automatically uninstalled for this
# What software is obsolete and will be automatically uninstalled for this
# RPM to run correctly once it's installed on a system?
# RPM to run correctly once it's installed on a system?
=== Obsoletes: PackageName ===
==== Obsoletes: PackageName ====
# The provides tag is used to specify a ‘virtual package’ that the packaged
# The provides tag is used to specify a ‘virtual package’ that the packaged
# software makes available when it is installed. Normally, this tag would
# software makes available when it is installed. Normally, this tag would
# be used when different packages provide equivalent services.
# be used when different packages provide equivalent services.
=== Provides: PackageName ===
==== Provides: PackageName ====
# This turns off automatic dependency processing that can sometimes
# This turns off automatic dependency processing that can sometimes
# cause problems
# cause problems
=== AutoReqProv: no ===
==== AutoReqProv: no ====
# The description is a slightly more verbose version of the summary
# The description is a slightly more verbose version of the summary
=== %description ===
==== %description ====
=== %name ===
==== %name ====
# %name is an implementation of http://domain.com for the SME Server.
# %name is an implementation of http://domain.com for the SME Server.
#This package has been integrated it into the SME Server and provides a
#This package has been integrated it into the SME Server and provides a
# The changelog records changes made with each version. Make sure these
# The changelog records changes made with each version. Make sure these
# are in exactly the right format, otherwise the RPM will not build.
# are in exactly the right format, otherwise the RPM will not build.
=== %changelog ===
==== %changelog ====
* Tue Feb 20 2003 Fred Foonly <fred@example.com>
* Tue Feb 20 2003 Fred Foonly <fred@example.com>
# for building. For instance, this is where you would apply patches if
# for building. For instance, this is where you would apply patches if
# you were using them.
# you were using them.
=== %prep ===
==== %prep ====
=== %setup ===
==== %setup ====
==== %patch0 -p1 ====
===== %patch0 -p1 =====
# The build section lists commands to run as part of the build process
# The build section lists commands to run as part of the build process
# This is where you can use a root/createlinks script to create events and
# This is where you can use a root/createlinks script to create events and
# action links.
# action links.
=== %build ===
==== %build ====
==== perl createlinks ====
===== perl createlinks =====
# The install section lists commands to run during the build phase to
# The install section lists commands to run during the build phase to
# refer to the directory rpms/BUILD/yourappname/root (or whatever's set
# refer to the directory rpms/BUILD/yourappname/root (or whatever's set
# in the BuildRoot line near the top of this spec file.
# in the BuildRoot line near the top of this spec file.
=== %install ===
==== %install ====
# clean out the build root, to make sure nothing old is hanging around
# clean out the build root, to make sure nothing old is hanging around
# in there
# in there
# This section will help clear out the build root before
# This section will help clear out the build root before
# building the RPM
# building the RPM
=== %clean ===
==== %clean ====
rm -rf $RPM_BUILD_ROOT
rm -rf $RPM_BUILD_ROOT
# on the SME Server. This may mean things like signalling events or
# on the SME Server. This may mean things like signalling events or
# running action scripts
# running action scripts
=== %preun ===
==== %preun ====
# The postun section lists commands to run after uninstalling the software
# The postun section lists commands to run after uninstalling the software
# on the SME Server. This may mean things like signalling events or
# on the SME Server. This may mean things like signalling events or
# running action scripts
# running action scripts
=== %postun ===
==== %postun ====
# The pre section lists commands to run prior to installing the software
# The pre section lists commands to run prior to installing the software
# on the e-smith system. This may mean things like signalling e-smith
# on the e-smith system. This may mean things like signalling e-smith
# events or running action scripts
# events or running action scripts
=== %pre ===
==== %pre ====
# The post section lists commands to run after installing the software
# The post section lists commands to run after installing the software
# on the e-smith system. This may mean things like signalling e-smith
# on the e-smith system. This may mean things like signalling e-smith
# events or running action scripts
# events or running action scripts
=== %post ===
==== %post ====
[[Category:Howto]]
[[Category:Howto]]
[[Category:SME Server Development Framework]]
[[Category:SME Server Development Framework]]
[[Category:Development Tools]]
[[Category:Development Tools]]
[[Category:SME9-Development]]
[[Category:SME9-Development]]
