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 ===
# 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 ===
# 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 ===
# 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 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 ===
# 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 ===
# 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 ====
# 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
# The %files statement lets us refer to an external file list that we
# The %files statement lets us refer to an external file list that we
# just generated, which is easier than trying to list them all by hand
# just generated, which is easier than trying to list them all by hand
%files -f %{name}-%{version}-filelist
%files -f %{name}-%{version}-filelist
# you'll want to leave the permissions as they are, but make the files
# you'll want to leave the permissions as they are, but make the files
# owned by user and group root
# owned by user and group root
%defattr(-,root,root)
%defattr(-,root,root)
