Mailinglist Archive: opensuse-kde (101 mails)
| < Previous | Next > |
Re: [opensuse-kde] RPMLINT errors in packages and conventions
- From: Tejas Guruswamy <masterpatricko@xxxxxxxxx>
- Date: Sun, 02 May 2010 10:23:09 +0100
- Message-id: <4BDD447D.7090804@xxxxxxxxx>
On 01/05/10 23:07, Johannes Obermayr wrote:
I'm sure it is frustrating to be "rejected", don't take it personally,
and feel free to ask for help.
it contains a library that might be used by other programs, then it
absolutely must and the above warnings (especially for libgluon) needs
to be fixed. If no external program will ever use it, you might get away
with ignoring this. I don't know enough about gluon to decide this. If
you haven't already, read
http://en.opensuse.org/Shared_Library_Packaging_Policy
script, noone puts significant effort there, so the spec files are
sometimes not the best examples.
Compare instead to openSUSE:Factory. These are in general the style that
SUSE expect the spec files to adhere to for future maintainability.
But anyway you are also comparing to the wrong packages, the main KDE SC
packages are absolute monsters to package with tens of subpackages and
so certain exceptions to the rules are made. For small packages like
yours follow the guidance you were given to structure the spec file.
thing about open source is that everyone can contribute and your
contributions will be judged on their own merits so don't be
disheartened, just use this as a learning experience.
for me ... I'll let you know anything I can contribute after I see the
source.
Regards,
Tejas
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
I tried several times submit requests for my gluon package toSorry, but if the errors were harmless, they wouldn't be there. While
KDE:KDE4:Playground. It was every time declined because of some (really)
harmless errors (it works and that is the main goal!).
I'm sure it is frustrating to be "rejected", don't take it personally,
and feel free to ask for help.
Last #39260:Whether gluon needs to follow the shlib-policy needs some thinking. If
"Reviewed - please fix : gluon-creator.x86_64: W: shlib-policy-missing-suffix
libgluon.x86_64: W: shlib-policy-missing-suffix Your package containing
shared libraries does not end in a digit and should probably be split.
libgluon.x86_64: W: shlib-policy-nonversioned-dir /usr/lib64/gluon Your
shared library package contains non-versioned directories. Those will not
allow to install multiple versions of the package in parallel."
it contains a library that might be used by other programs, then it
absolutely must and the above warnings (especially for libgluon) needs
to be fixed. If no external program will ever use it, you might get away
with ignoring this. I don't know enough about gluon to decide this. If
you haven't already, read
http://en.opensuse.org/Shared_Library_Packaging_Policy
When comparing with kdebase4 [K:K:U:D] I am asking me what is worse-rated.You are comparing to the wrong place. K:K:U:D is created by an automated
When comparing with kdegames4 [K:K:U:D] I see something criticized in #38639
(structure of spec file).
script, noone puts significant effort there, so the spec files are
sometimes not the best examples.
Compare instead to openSUSE:Factory. These are in general the style that
SUSE expect the spec files to adhere to for future maintainability.
But anyway you are also comparing to the wrong packages, the main KDE SC
packages are absolute monsters to package with tens of subpackages and
so certain exceptions to the rules are made. For small packages like
yours follow the guidance you were given to structure the spec file.
Please note:Most of us are not developers, most of us have day jobs. But the nice
I am not a developer. I am study as a civil servant in Germany and my exams
are in Sep. So I have to learn something about law, order and federal
administration but not programming ...
thing about open source is that everyone can contribute and your
contributions will be judged on their own merits so don't be
disheartened, just use this as a learning experience.
Thanks for telling me your opinions or patches for fixing it ...I'd have a look at your spec file but the OBS is currently timing out
Johannes
for me ... I'll let you know anything I can contribute after I see the
source.
Regards,
Tejas
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
| < Previous | Next > |