Good design habits for SPEC files for rpm

[PatMcDonagh]

hi folks,

Please excuse me if I have posted in the wroing area but i hope not.

I am reviewing some of the build manage files in a section i have taken over.

rpm is being used to build the packages and I am going through a .spec file

I have some doubts as to how it has been laid out (based on what i have picked up from the various sites that explain the layout of .spec files). I was wondering if there was a definitive list of tips and do's and don'ts re how to define sa spec file.

Any help directing me would be appreciated.

[PabloTwo]

Hello Pat, and welcome to the forum.

If you are building rpm packages specifically for Fedora, then there is a packaging guide to help you with that.

[leigh123linux]

Heres another link

http://fedoraproject.org/wiki/How_to...an_RPM_package

[PatMcDonagh]

Leigh, Pablo,

thanks for the quick reply. It is much appreciated.

Can i just ask if its normal for a spec file to trigger a ./configure & gmake while still in the %prep area and before the %build area has even been declared.

I have noticed that the folloeing command is being issued after All source files have been established

./prod-configure.sh
gmake > make.out 2>&1

thereafter the resultant binaries are copied then the %build line is declared followed directly by %files and the files to be included in the package.

My understanding is that the make is defined and executed within %build and the the file i have inherited has gone outside of what is good practice.

[leigh123linux]

%prep is used for unpacking and patching the source


Heres a sample spec

Name:           
Version:        
Release:        1%{?dist}
Summary:        

Group:          
License:        
URL:            
Source0:        
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires:  
Requires:       

%description


%prep
%setup -q


%build
%configure
make %{?_smp_mflags}


%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT


%clean
rm -rf $RPM_BUILD_ROOT


%files
%defattr(-,root,root,-)
%doc



%changelog

./configure shouldn't be used directly, use %configure instead


the %configure macro expands to

[leigh@main_pc Desktop]$ rpm -qf %configure
error: file /home/leigh/Desktop/
  CFLAGS="${CFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic}" ; export CFLAGS ; 
  CXXFLAGS="${CXXFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic}" ; export CXXFLAGS ; 
  FFLAGS="${FFLAGS:--O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -I/usr/lib64/gfortran/modules}" ; export FFLAGS ; 
  ./configure --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu \
    --target=x86_64-redhat-linux-gnu \
    --program-prefix= \
    --prefix=/usr \
    --exec-prefix=/usr \
    --bindir=/usr/bin \
    --sbindir=/usr/sbin \
    --sysconfdir=/etc \
    --datadir=/usr/share \
    --includedir=/usr/include \
    --libdir=/usr/lib64 \
    --libexecdir=/usr/libexec \
    --localstatedir=/var \
    --sharedstatedir=/var/lib \
    --mandir=/usr/share/man \
    --infodir=/usr/share/info