August 2008 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] New ncurses version in STABLE, now with thread safe support
by Dr. Werner Fink 14 Aug '08

14 Aug '08

Hi, just submitted a new ncurses version 5.6 pachlevel 20080405 to factory. Please note that beside the normal libncurses 5.6 we now have libncurses 6.0. The later has two versions one is thread safe and one is thread safe combined with wide character support. This together with the libncurses 5.6 and ts normal and wide characters support requires *FOUR* different header files. To be noted: do *never* use wrong headers with any from the libraries above as this are binary incomaptible. To use the normal vesion you may link simply with the value returned from ncurses5-config --libs e.g. `-L/usr/lib -lncurses', this uses libncurses.so.5.6. Remark: the command `ncurses5-config --cflags' returns nothing as the headers of libncurses.so.5.6 are found in the standard include path. For the version with wide character support the value returned from ncursesw5-config --cflags ncursesw5-config --libs have to be used for compiling and and linkage, which use then libncursesw.so.5.6 then. For the new thread support, the new ABI 6 has to be used which is automatically returned from ncursest6-config --cflags ncursest6-config --libs to be used for compiling and and linkage, which use then libncursest.so.6.0 then. Last but not least for new thread support combined with wide character support also the new ABI 6 has to be used which is automatically returned from ncursestw6-config --cflags ncursestw6-config --libs to be used for compiling and and linkage, which use then the libncursestw.so.6.0. For more informations you may read /usr/share/doc/packages/ncurses/README.devel for further informations. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 11

[opensuse-packaging] Runlevel override management
by Jan Engelhardt 11 Aug '08

11 Aug '08

Bringing to your attention, bug #310539, where I wrote: >Unfortunate thing is that upgrading a package replaces >/etc/init.d/PROGRAM, which means it gets new "Default-Start" and >"Default-Stop" tags, and running insserv then updates the links in >/etc/init.d/rc?.d according to these tags, effectively trashing your >own, personal preferential, runlevel settings [one has made via chkconfig] > >This affects any service. Any idea how to reasonably give way for >unoverridable personal settings? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Broken package after update
by Karl Eichwalder 08 Aug '08

08 Aug '08

Probably a normal problem, but I do not know the solution or work around: In the past, we used to ship sgmltool on our standard media. Now it is missing and thus, after the update from 10.3 to 11.0 a broken package is left. See https://bugzilla.novell.com/show_bug.cgi?id=412525 IIRC, sgmltool is still available in the FTP installation. Dropping it as unmaintained probably is not an option. Wondering what is the best way out off this dilemma? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

[opensuse-packaging] .la files, shlib-policy, autotools
by Andrew Jorgensen 07 Aug '08

07 Aug '08

The shared library policy says: - Avoid packaging libtool config files (.la files). In general they are not needed if you do not package a static library. If in doubt, ask. I would like more clarification on when they are needed and not but more importantly: Can anyone tell me what is the correct autotools way to control if these files get installed alongside the .so? It seems they generally get created and installed even if you are not building a static library and using rm in the %install section seems hackish. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 5

[opensuse-packaging] Broken package after update
by Karl Eichwalder 07 Aug '08

07 Aug '08

Probably a normal problem, but I do not know the solution or work around: In the past, we used to ship sgmltool on our standard media. Now it is missing and thus, after the update from 10.3 to 11.0 a broken package is left. See https://bugzilla.novell.com/show_bug.cgi?id=412525 IIRC, sgmltool is still available in the FTP installation. Dropping it as unmaintained probably is not an option. Wondering what is the best way out off this dilemma? -- Karl Eichwalder --------------------------------------------------------------------- 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] Broken package after update
by Karl Eichwalder 07 Aug '08

07 Aug '08

Probably a normal problem, but I do not know the solution or work around: In the past, we used to ship sgmltool on our standard media. Now it is missing and thus, after the update from 10.3 to 11.0 a broken package is left. See https://bugzilla.novell.com/show_bug.cgi?id=412525 IIRC, sgmltool is still available in the FTP installation. Dropping it as unmaintained probably is not an option. Wondering what is the best way out off this dilemma? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] SPEC file licensing / Copyright
by Dirk Mueller 05 Aug '08

05 Aug '08

Hi, The licensing header that is added automatically when submissions go through openSUSE:Factory has been updated to address two concerns that were raised, namely * Licensing of the spec file itself is defined more clearly, especially for packages with non-free licenses. * Copyright headers are preserved. See below for more information. The new licensing header is: === Cut === # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. === Cut === the .spec files will be automatically updated over time with this licensing header as they're going through the Factory submission review process. Feedback, or questions regarding this new Licensing header is appreciated. An artefact of the previous licensing update handler was that it stripped any leading comments from the spec file, so including any of your own copyright or licensing headers that you might have added. It still does that, however lines that match the pattern ^#\s*Copyright\s* like for example # Copyright Donny McFoo <foo(a)example.com> are preserved verbatim if they're added to the .spec file licensing header manually. Please make use of this feature to clarify your copyright on a certain spec file if you've made significant contributions to it. Greetings, Dirk --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0