June 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] packaging a library according to Shared_Library_Packaging_Policy
by Marcus Hüwe 07 Jun '07

07 Jun '07

Hi, I'm trying to build a lib properly according to the "Shared Library Packaging Policy". According to this document a lib$NAME$NUM package contains only the shared object itself. Now I want to add some %doc files (like README, COPYING AUTHORS etc.) but I'm not quite sure if i can add the the lib$NAME$NUM rpm. So where do i have to place the %doc files? (i can't find a similar case in the "Exceptions"-section) Thanks in advance. Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] libbz2 has been renamed to libbz2-1
by Ladislav Michnovič 04 Jun '07

04 Jun '07

Hello. The libbz2 package has been renamed to libbz2-1 accordint to the policy : http://en.opensuse.org/Shared_Library_Packaging_Policy . Regards Ladislav Michnovic. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 11

[opensuse-packaging] rpmlint checks in Factory
by Dirk Mueller 01 Jun '07

01 Jun '07

Hi, There are new, considered to be experimental, checks for rpmlint diagnostics in Factory. So far, the following checks are enabled: arch-dependent-file-in-usr-share 590 infopage-not-gzipped 540 wrong-script-interpreter 533 arch-independent-package-contains-binary-or-object 499 library-without-ldconfig-postun 400 shlib-with-non-pic-code 223 files-duplicated-waste 100 summary-not-capitalized 63 spurious-executable-perm 50 devel-file-in-non-devel-package 50 wrong-file-end-of-line-encoding 1 Other checks are also perform and printed in the log file (autobuild only, opensuse buildservice will follow later), but they _do_ _not_ _matter_ right now. The number behind the check name above is the badness score that was assigned to it. if any build has a score above 1000, it is currently failed. There are some packages which might suffer from false positives of above checks. Please, in order to help clean that up, file a bugreport against me (dmueller(a)novell.com) mentioning package name and check that you consider false, and I'll fix it ASAP. About the warning only checks: If you encounter any of such checks that you feel are wrong, are not complying our best practices or are exceptions that should be suppressed, PLEASE tell me about it! Do not hack around them! So, if you have a failed build today, please look ONLY for '^E:' in the logfile to figure out why it was failed. Each line has a badness score besides it. Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 14