New Package: gcm (GNOME Clipboard Manager)

[Gijs Hollestelle]

On 6/30/05, P229 <p229.357 at gmail.com> wrote:
> GNOME Clipboard Manager facilitates management of clipboard contents
> and, of particular importance, allows access to clipboard contents even
> after the clip source is closed.
> 
> SRPM, spec file, etc.: https://amdg.dyndns.org/~p229/index.html

Hi,

I'm not really an expert in these reviews, but I'll have a try at it
as I would like to see gcm included (or some other way to preserve the
clipboard).

Good:
- Source matches upstream
- License is OK (GPL)

Not so good:
- rpmlint: 
W: gcm non-standard-group X11/Utilities
W: gcm no-version-in-last-changelog
W: gcm conffile-without-noreplace-flag /etc/gconf/schemas/gcmapplet.schemas
E: gcm library-without-ldconfig-postin /usr/lib/librtftohtml.so.0.2.0
E: gcm library-without-ldconfig-postun /usr/lib/librtftohtml.so.0.2.0
E: gcm library-without-ldconfig-postin /usr/lib/libgcm.so.0.2.0
E: gcm library-without-ldconfig-postun /usr/lib/libgcm.so.0.2.0
E: gcm zero-length /usr/share/doc/gcm-2.0.4/NEWS
W: gcm non-standard-dir-in-usr libexec
- Missing build requires: gnome-panel-devel
- Why the if ! -x configure test in %build? I would just assume the
upstream tarball has a configure script, so just get rid of the ! -x
configure test.
- There are a lot of installed but unpackaged .h .la and .pc files,
maybe consider making a gcm-devel subpackage and putting these files
there?
- There are plugins installed but unpackaged

- There are a lot of other unpackaged files, which are being worked
around by using:
%define _unpackaged_files_terminate_build 0
%define _missing_doc_files_terminate_build 0
I think it would be better to remove the unwanted files than to do it
like this.

In order to resolve the last issue, see for example Dries' package of gcm:
http://dries.ulyssis.org/rpm/packages/gcm/gcm-spec.html

Greets,
  Gijs