[Bug 881431] Review Request: zathura-pdf-poppler - PDF support for zathura via poppler

[bugzilla at redhat.com]

Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=881431

--- Comment #8 from Eduardo Echeverria <echevemaster at gmail.com> ---
(In reply to comment #7)
> Hi Eduardo.
> 
> His source rpm is for Fedora 16. If it was for EPEL5, then it should be
> packaged as el5 ...
> This leads me to think to Fedora packaging rules. :)

Hi Antonio, not necessarily, remember that if you don't have a specific release
of fedora to build, not mean you can not offer the package for different
branches, mock or koji, takes care of that.

look in /etc/mock the available configurations, You'll get output like this:

echevemaster at echevemaster mock$ ls

default.cfg            fedora-17-i386.cfg      fedora-5-x86_64-epel.cfg
epel-5-i386.cfg        fedora-17-ppc64.cfg     fedora-devel-i386.cfg
epel-5-ppc.cfg         fedora-17-ppc.cfg       fedora-devel-ppc64.cfg
epel-5-x86_64.cfg      fedora-17-s390.cfg      fedora-devel-ppc.cfg
epel-6-i386.cfg        fedora-17-s390x.cfg     fedora-devel-x86_64.cfg
epel-6-ppc64.cfg       fedora-17-sparc64.cfg   fedora-rawhide-arm.cfg
epel-6-x86_64.cfg      fedora-17-sparc.cfg     fedora-rawhide-armhfp.cfg
fedora-16-arm.cfg      fedora-17-x86_64.cfg    fedora-rawhide-i386.cfg
fedora-16-i386.cfg     fedora-18-arm.cfg       fedora-rawhide-ppc64.cfg
fedora-16-ppc64.cfg    fedora-18-armhfp.cfg    fedora-rawhide-ppc.cfg
fedora-16-ppc.cfg      fedora-18-i386.cfg      fedora-rawhide-s390.cfg
fedora-16-s390.cfg     fedora-18-ppc64.cfg     fedora-rawhide-s390x.cfg
fedora-16-s390x.cfg    fedora-18-ppc.cfg       fedora-rawhide-sparc64.cfg
fedora-16-sparc64.cfg  fedora-18-s390.cfg      fedora-rawhide-sparc.cfg
fedora-16-sparc.cfg    fedora-18-s390x.cfg     fedora-rawhide-x86_64.cfg
fedora-16-x86_64.cfg   fedora-18-x86_64.cfg    logging.ini
fedora-17-arm.cfg      fedora-5-i386-epel.cfg  site-defaults.cfg
fedora-17-armhfp.cfg   fedora-5-ppc-epel.cfg

or just do a scratch build
koji build --scratch dist-5E-epel foo.rpm

Moreover, how recognize that probably a packager wants to offer its package on
EPEL5 ?

- Buildroot is present 
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

- rm -rf $RPM_BUILD_ROOT is present at the beginning of %install

- %clean section is present

Although it is always good to ask what are intentions of packager.

François I'm sorry for the flood, But I thought it necessary to explain this to
Antonio

-- 
You are receiving this mail because:
You are on the CC list for the bug.