dglent
commented
9 years ago Because they are in /etc/lib Take the example in the spec of Mageia: https://svnweb.mageia.org/packages/cauldron/boomaga/current/SPECS/boomaga.spec?view=markup
----- Mail original -----
De: "Oleg" notifications@github.com À: "Boomaga/boomaga" boomaga@noreply.github.com Envoyé: Lundi 29 Juin 2015 15:52:19 Objet: [boomaga] SPEC file for building RPM x86_64 (#27)
I try to do valid RPM package for Fedora x86_64. There is worked example of SPEC file (but not valid according to the guidelines): Name: boomaga Version: 0.7.0 Release: 1%{ ? dist} Summary: Boomaga is a virtual printer for viewing a document before printing
License: GPLv2 and LGPLv2+ URL: http://boomaga.github.io Source0: %{name}-%{version}.tar.gz
BuildRequires: cmake,cups-devel,poppler-devel,poppler-cpp-devel,qt5-qtbase-devel,qt5-qttools-devel,snappy-devel Requires: cups
%description Boomaga (BOOklet MAnager) is a virtual printer for viewing a document before printing it out using the physical printer. The program is very simple to work with. Running any program, click “print” and select “Boomaga ” to see in several seconds (CUPS takes some time to respond) the Boomaga window open. If you print out one more document, it gets added to the previous one, and you can also print them out as one.
%prep %setup -q
%build mkdir build cd build cmake ..
%make_install
%files %defattr(0755,root,root,-) /usr/lib/cups/backend/boomaga /usr/lib/cups/filter/boomaga_pstopdf /usr/local/bin/boomaga /usr/local/lib/boomaga/boomagabackend /usr/local/lib/boomaga/boomagamerger /usr/local/share/applications/boomaga.desktop /usr/local/share/boomaga/translations/boomaga_cs.qm /usr/local/share/boomaga/translations/boomaga_de.qm /usr/local/share/boomaga/translations/boomaga_el.qm /usr/local/share/boomaga/translations/boomaga_fr.qm /usr/local/share/boomaga/translations/boomaga_it.qm /usr/local/share/boomaga/translations/boomaga_lt.qm /usr/local/share/boomaga/translations/boomaga_pl_PL.qm /usr/local/share/boomaga/translations/boomaga_ru.qm /usr/local/share/boomaga/translations/boomaga_uz@Latn.qm /usr/local/share/dbus-1/services/org.boomaga.service /usr/local/share/icons/hicolor/128x128/apps/boomaga.png /usr/local/share/icons/hicolor/16x16/apps/boomaga.png /usr/local/share/icons/hicolor/32x32/apps/boomaga.png /usr/local/share/icons/hicolor/64x64/apps/boomaga.png /usr/local/share/mime/packages/boomaga.xml /usr/share/ppd/boomaga/boomaga.ppd %attr(0644,root,root) %doc /usr/local/share/man/man1/boomaga.1.gz
%changelog * Mon Jun 22 2015 Oleg
The guidelines ( https://fedoraproject.org/wiki/How_to_create_an_RPM_package ) said: " You should follow the Filesystem Hierarchy Standard (FHS). Executables go in /usr/bin, global configuration files go in /etc, libraries go into /usr/lib (or /usr/lib64) and so on. Do not install files into /opt or /usr/local. " There is valid according to the guidelines - https://fedoraproject.org/wiki/Packaging:Cmake - SPEC file (but it doesn't work for x86_64. See %files section): Name: boomaga Version: 0.7.0 Release: 1%{ ? dist} Summary: Boomaga is a virtual printer for viewing a document before printing
License: GPLv2 and LGPLv2+ URL: http://boomaga.github.io Source0: %{name}-%{version}.tar.gz
BuildRequires: cmake,cups-devel,poppler-devel,poppler-cpp-devel,qt5-qtbase-devel,qt5-qttools-devel,snappy-devel Requires: cups
%description Boomaga (BOOklet MAnager) is a virtual printer for viewing a document before printing it out using the physical printer. The program is very simple to work with. Running any program, click “print” and select “Boomaga ” to see in several seconds (CUPS takes some time to respond) the Boomaga window open. If you print out one more document, it gets added to the previous one, and you can also print them out as one.
%prep %setup -q
%build %cmake . make %{ ? _smp_mflags}
%install make install DESTDIR=%{buildroot}
%files %defattr(755,root,root,-) %{_libdir}/cups/backend/boomaga %defattr(-,root,root,-) %{_libdir}/cups/filter/boomaga_pstopdf %{_bindir}/boomaga %{_libdir}/boomaga/boomagabackend %{_libdir}/boomaga/boomagamerger %{_datadir}/applications/boomaga.desktop %{_datadir}/boomaga/translations/ %{_datadir}/dbus-1/services/org.boomaga.service %{_datadir}/icons/hicolor/ \ %{_datadir}/mime/packages/boomaga.xml %{_datadir}/ppd/boomaga/boomaga.ppd
%doc COPYING GPL LGPL README.md %{_mandir}/man1/boomaga.1.gz
%changelog * Mon Jun 22 2015 Oleg Ekhlakov < subspam@mail.ru > 0.7.0-1.fc21.R
- Initial version of the package It is aborted with an error:
error: File not found: /home/oleg/rpmbuild/BUILDROOT/boomaga-0.7.0-1.fc21.R.x86_64/usr/lib64/cups/backend/boomaga
error: File not found: /home/oleg/rpmbuild/BUILDROOT/boomaga-0.7.0-1.fc21.R.x86_64/usr/lib64/cups/filter/boomaga_pstopdf
error: File not found: /home/oleg/rpmbuild/BUILDROOT/boomaga-0.7.0-1.fc21.R.x86_64/usr/lib64/boomaga/boomagabackend
error: File not found: /home/oleg/rpmbuild/BUILDROOT/boomaga-0.7.0-1.fc21.R.x86_64/usr/lib64/boomaga/boomagamerger
As far as I understood, %{_libdir} should be /usr/lib for x32 only and %{_libdir} should be /usr/lib64 for x86_64 only. The guidelines said: " Unfortunately, many programs do not follow the FHS by default. In particular, architecture-independent libraries get placed in /usr/lib instead of /usr/share. The former is for architecture-dependent libraries, while the latter is for architecture-independent libraries, which means that systems with different CPU architectures can share /usr/share. There are many exceptions in Fedora (such as Python and Perl), but Fedora applies this rule more strictly than some distributions. rpmlint will generally complain if you put anything other than ELF files into /usr/lib. " It seems that in the project need to change the location of the files (for the x86_64 architecture), but I don't know how to do it correctly : /usr/lib/cups/backend/boomaga -> /usr/lib64/cups/backend/boomaga /usr/lib/cups/filter/boomaga_pstopdf -> /usr/lib64/cups/filter/boomaga_pstopdf /usr/lib/boomaga/boomagabackend -> /usr/lib64/boomaga/boomagabackend /usr/lib/boomaga/boomagamerger -> /usr/lib64/boomaga/boomagamerger — Reply to this email directly or view it on GitHub .
Dimitrios Glentadakis
XOlegator
SokoloffA
I try to do valid RPM package for Fedora x86_64. There is worked example of SPEC file (but not valid according to the guidelines):
The guidelines (https://fedoraproject.org/wiki/How_to_create_an_RPM_package) said: "You should follow the Filesystem Hierarchy Standard (FHS). Executables go in /usr/bin, global configuration files go in /etc, libraries go into /usr/lib (or /usr/lib64) and so on. Do not install files into /opt or /usr/local." There is valid according to the guidelines - https://fedoraproject.org/wiki/Packaging:Cmake - SPEC file (but it doesn't work for x86_64. See %files section):
It is aborted with an error:
As far as I understood, %{_libdir} should be /usr/lib for x32 only and %{_libdir} should be /usr/lib64 for x86_64 only. The guidelines said: "Unfortunately, many programs do not follow the FHS by default. In particular, architecture-independent libraries get placed in /usr/lib instead of /usr/share. The former is for architecture-dependent libraries, while the latter is for architecture-independent libraries, which means that systems with different CPU architectures can share /usr/share. There are many exceptions in Fedora (such as Python and Perl), but Fedora applies this rule more strictly than some distributions. rpmlint will generally complain if you put anything other than ELF files into /usr/lib." It seems that in the project need to change the location of the files (for the x86_64 architecture), but I don't know how to do it correctly: /usr/lib/cups/backend/boomaga -> /usr/lib64/cups/backend/boomaga /usr/lib/cups/filter/boomaga_pstopdf -> /usr/lib64/cups/filter/boomaga_pstopdf /usr/lib/boomaga/boomagabackend -> /usr/lib64/boomaga/boomagabackend /usr/lib/boomaga/boomagamerger -> /usr/lib64/boomaga/boomagamerger