[Bug 507083] Review Request: poco - C++ class libraries for network-centric applications

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=507083





--- Comment #3 from Maxim Udushlivy <udushlivy at mail.ru>  2009-06-22 17:16:07 EDT ---
Hello, and thank you for a quick reply!

*1. The proposed split has a simple rationale - move rarely used features to
separate packages and keep the total number of packages to the minimum:

'poco' - contains retail builds of the general-purpose libraries
'poco-extra' - retail builds of the libraries that are either rarely used or
pull peculiar dependencies
'poco-debug' - debug builds (POCO makefiles produce them) of all libraries,
they are used only during development of the POCO-based applications for
testing purposes
'poco-devel' - headers and .so links to retail and debug libraries
'poco-debuginfo' - automatically generated package with debug-related
information

But I agree to further split 'poco-extra' into three separate 'poco-mysql',
'poco-odbc' and 'poco-zip'. This variant (although requiring increased typing
from the .spec compositor) is more reasonable.

*2. I am not sure that 'poco-debug' has to be split because 'poco-devel', as a
development package, should pull everything anyway (see
http://packages.debian.org/squeeze/libpoco-dev which partially demonstrates
this). But it may be renamed to 'poco-testing' in order to avoid associations
with 'poco-debuginfo'.

*3. The perl build dependency is mentioned as "/usr/bin/perl" instead of "perl"
in order to emphasize the dependency on a particular file (a CLI program in
this case) but not on a package; probably the same situation as with
"/sbin/ldconfig" being used instead of "glibc".

-- 
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.