Red Hat Bugzilla – Bug 222043
Review Request: gnomescan - Gnome Scanner Utility
Last modified: 2007-11-30 17:11:52 EST
Spec URL: ftp://czar.eas.yorku.ca/pub/gnomescan/gnomescan.spec
SRPM URL: ftp://czar.eas.yorku.ca/pub/gnomescan/gnomescan-0.4.0.2-1.src.rpm
Description: Gnome Scan aim to provide a sane scan infrastructure. Flegita provide
app and plugin on top of Gnome Scan for the desktop
I am not an official reviewer, so consider this a pre-review.
Builds in mock on i386 fedora core 6. Installs and runs - however I haven't got
a scanner, so I cannot test functionality.
rpmlint produces one error:
W: gnomescan-devel no-documentation
Which I suppose is fine, since the documentation belongs in the main package and
not in the devel package.
Package and spec file are correctly named
Language and license are fine.
find_lang is correctly used for locales.
ldconfig is correctly called in %post and %postun
Packages correctly own directories.
Correctly handles pkgconfig files.
Header files are in devel package.
Includes a .desktop file that is correctly installed.
What I am unsure about is this. It seems to me that this includes both gnomescan
(flegita - the actual scanning application) and libgnomescan. Should the two be
(In reply to comment #1)
> I am not an official reviewer, so consider this a pre-review.
Thanks for looking at it.
> What I am unsure about is this. It seems to me that this includes both gnomescan
> (flegita - the actual scanning application) and libgnomescan. Should the two be
> packaged separately?
I believe it's okay as is, seems like flegita is sort of a codename or nickname,
and people who want to use the libs part can make use of the -devel subpackage.
(In reply to comment #2)
> (In reply to comment #1)
> > I am not an official reviewer, so consider this a pre-review.
> Thanks for looking at it.
> > What I am unsure about is this. It seems to me that this includes both gnomescan
> > (flegita - the actual scanning application) and libgnomescan. Should the two be
> > packaged separately?
I don' think we need both packaged separately.
> I believe it's okay as is, seems like flegita is sort of a codename or nickname,
> and people who want to use the libs part can make use of the -devel subpackage.
However, I found that you don't need pkgconfig as BR for main package.
Also, do we really need libtool as BR and all other make LIBTOOL? I removed them
and did mock test and it went fine.
Can you check that with testing application??
Also i found you have option to create a separate package for gimp-plugin that
will contains single file in its installation.
(In reply to comment #3)
> However, I found that you don't need pkgconfig as BR for main package.
Maybe not explicitly (probably some other dependencies pulled it in inside mock
for you), if you check the configure log you'll see that it checks for the
presence of pkgconfig, so its needed for building.
> Also, do we really need libtool as BR and all other make LIBTOOL? I removed them
> and did mock test and it went fine.
Did you run rpmlint on the resulting binary? If you did, you will have found out
it has some rpath issues caused by using the libtool script bundled with the
package. That's the reason for the libtool as BR and all other make LIBTOOL.
As for your other comment on separate package for gimp-plugin, I don't think its
necessary just for a single file. Or is there some technical reason(s) for it to
be a separate package?
> Can you check that with testing application??
My argument for maybe packaging libgnomescan separately is that if someone
produces another scanning application, and depends on gnomescan-devel we
suddenly have two different scanning applications installed, since
gnomescan-devel depends on gnomescan.
It is probably a minor detail at this, and is all depends on how you expect
libgnomescan to be used by other applications.
+ package builds in mock (development i386).
+ rpmlint is silent for SRPM and RPMS.
+ source files match upstream.
+ package meets naming and packaging guidelines.
+ specfile is properly named, is cleanly written
+ Spec file is written in American English.
+ Spec file is legible.
+ dist tag is present.
+ build root is correct.
+ license is open source-compatible. License text included in package.
+ %doc is small; no -doc subpackage required.
+ %doc does not affect runtime.
+ BuildRequires are proper.
+ %clean is present.
+ package installed properly.
+ Macro use appears rather consistent.
+ Package contains code Not contents.
+ no static libraries present.
+ no gnomescan.pc and gnomescanui.pc files present.
+ -devel subpackage exists
%post -p /sbin/ldconfig
%postun -p /sbin/ldconfig
+ no .la files.
+ translations are available
+ Dose owns the directories it creates.
+ no duplicates in %files.
+ no scriptlets used.
+ Desktop files are handled correctly in spec.
+ file permissions are appropriate.
+ gui app.
Package Rename CVS Request
Old name: gnomescan
New name: gnome-scan
Short Description: Gnome solution for scanning in the desktop on top of libsane
Branches: F-7 F-8 devel
Cvsextras Commits: yes
I have created the new gnome-scan package.
Please follow the end of life procedure for the gnomescan package:
Also, make sure the new package has the right Obsoletes/Provides: