Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
--- Comment #8 from Richard Shaw <hobbes1069(a)gmail.com> 2011-12-02 12:15:35 EST ---
(In reply to comment #7)
(In reply to comment #6)
Why are you pinging? The packages from comment #4 are current.
Because it wasn't a rhetorical question and because you didn't answer the
question until now :)
And no, I do not want to rename this package into Coin and want to
Coin2/Coin3 in parallel, because they are not 100% compatible (as you
experienced with Pivy) and because of licensing issues (Coin1 was LGPL,
Coin2/Coin3 are GPLv2 (Note GPLv2, not GPLv2+; The next Coin likely will be
That's all I was looking for was an explanation.
I build packages on F15 x86_64 which have the following rpmlint output:
$ rpmlint *.rpm
Coin3.src:57: W: unversioned-explicit-provides pkgconfig(Coin)
Coin3.x86_64: W: shared-lib-calls-exit /usr/lib64/libCoin.so.60.1.3
Coin3.x86_64: E: incorrect-fsf-address /usr/share/doc/Coin3-3.1.3/LICENSE.GPL
Coin3-devel.x86_64: W: read-error /usr/lib64/pkgconfig/Coin.pc [Errno 2] No
such file or directory:
Coin3-devel.x86_64: W: dangerous-command-in-%post rm
4 packages and 0 specfiles checked; 1 errors, 4 warnings.
I think most of this can be ignored either because it's an artifact of
alternatives (unversioned-explicit-provides, read-error,
dangerous-command-in-%post) or upstream is currently unlikely to to care
The only change I feel pretty strongly about is creating a separate doc
sub-package. Currently the devel package is 55MB, most of which is
documentation and the most common use is more likely to be from someone, like
myself, that just needs it as a build requirement and have no intention of
doing any direct development using Coin3.
Full review to follow.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.