Re: [opensuse-packaging] openSUSE 11.0 - call for package updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cristian RodrÃguez wrote: | I do checked them ;) and critized them with patches :-) | you can now check out the improved versions | osc co home:elvigia libwps | osc co home:elvigia libwpg Hello, thank you for your work. I would like to comment though on one thing. I don't thing that it is really necessary to have the package name redundant like libwps-0_1-1. All libraries that I maintain, I make the build system the way that between two minor releases they are parallel installable including the devel files. The reason is that they are C++ libraries and adding a method to an interface class makes them to break ABI. And since different products that depend on them might have different release cycles, it is highly likely that one will have to have two versions during some time on the system. That is why the sonames are libwps-0.1.so.1.X.Y as well as libwpd-0.8.so.8.X.Y. The other reason is that win32 build using libtool is addint the libtool versioning normally to the dll name, so I avoid the libtool versioning in the makefiles and rely on the library name only. That is why I would propose that the packages produced be called libwpg1 libwpg1-devel and libwpg-tools. This would be enough to distinguish them without really making the name too complicated. The libwpg-tools I would leave it without the versioning, because libwpg-tools produced by libwpg-0.1.x will not be parallel installable with those produced by libwpg-0.2.x. Thanks again for your work and please, people, consider this considerations. Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHjPt5u9a1imXPdA8RArMHAJ4gwz9J1o0rzeEYuqYH/S6+GBvRIACfe5+I uotP52yKiTv6wwxi9SeTjI4= =6iOy -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] openSUSE 11.0 - call for package updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcus Meissner wrote: | pmladek libwpd 0.8.12 0.8.13 I would even urge if it possible to package libwpg and libwps. Both of them are used for OpenOffice.org and AbiWord, libwpg is even used for upcoming inkscape 0.46. Using one system version of then instead of statically linking different versions in different products would help even to save some space on the install media. Not speaking about the hassle a security update would be if one had to rebuild OpenOffice.org and Inkscape instead of just upgrading a little tiny library. And it is not like these libraries are under-maintained. Apart a thorough pro-active QA ever release is exposed to, I am able to fix issues in a time of hours and release a new upstream version if needed. Moreover, all these libraries are packaged currently in my BS home project - home:fstrba. It is possible that the spec files could be criticized by the public and have some little problems, but as a starting point, they are reputed to work on all platforms I am building for. OK, just preaching for my own parish, so if you feel like, ignore me :-) Cheers Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHiLpIu9a1imXPdA8RAq+fAJ4tZ5ualybjBEMiqG0oKHaukZtuigCfVJ+0 P2M8iEAC6jkE2bQvHbGjVb8= =q1lw -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] Library naming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jan Engelhardt wrote: Hi, I notice, for example, -rw-r--r-- 1 455 5200 66727 Sep 22 00:02 libelf0-devel-0.8.9-17.i586.rpm while I agree with the new naming scheme (libelf0), I do not for -devel packages that cannot reasonably be installed alongside each other. Think of libelf0-devel and libelf1-devel which both provided a file with the same path. Without starting religious issues, would not it be better to just continue on naming such devel packages libelf-devel, without a number, like Debian? That would also reduce newly Obsoletes: tags, because now, a libelf1-devel would need an Obsoletes/Conflicts: libelf0-devel, and that's not really helping. This is not necessarily true for all libraries. Libwpd 0.7.x and libwpd 0.8.x can be installed both as shared libraries and developer packages alongside. For libwpd-0.9.x it will be the same. In that case, having libwpd8 and libwpd8-devel would be completely justified. http://libwpd.sf.net Cheers Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHBR0Uu9a1imXPdA8RAlbeAJwJbpd5Py/xUtK7svzkghlIHkk2twCfSBuR 3F3aH42UPXMl8wecW1uKUL8= =T/9N -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] GCC 4.3 transition and fallout in your packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Guenther wrote: Geometry.cpp: In member function 'const Magick::Geometry Magick::Geometry::operator=(const std::string)': Geometry.cpp:191: error: 'strcpy' was not declared in this scope make[3]: *** [Geometry.lo] Error 1 which hints at that you should include cstring, the C++ standard include name of the C string.h header. The rule of thumb is to look in which C header the missing function is in and then include the C++ variant which has a 'c' prepended and the '.h' stripped off. As a rule of thumb I would mainly advise to use #include string.h, if the file that contains the strcpy does not have the std:: namespace flattened. cstring puts the string.h functions into the std:: namespace and adding namespace flattening where upstream did not intend to put it might be broken, since some those flattenings work well with gcc, but are completely broken with MSVC++ or Sun Studio :-) BTW, for libwpg, libwpd, wpd2sxw and wpg2sxw, libraries that I maintain, the gcc 4.3 changes are incorporated in corresponding CVS. I will release them little by little when we reach a critical amount of bug-fixes (I have released all of them less then a month ago :-() Cheers Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG+Awku9a1imXPdA8RAq3vAJ40B/Q2E1hq/+ymq6VqISqd+svPewCfaIbM uoBmJx6PCkqRVwmkE3Dgenw= =u8Bl -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
