On 11/25/2011 11:49 PM, David Disseldorp wrote:
Hi Ken,
On Fri, 25 Nov 2011 13:04:59 +1100
Ken McDonell<kenj@xxxxxxxxxxxxxxxx> wrote:
I'm posting here in the hope that someone cares about PCP on the SUSE
distributions (sgi?).
I loaded the recently released openSUSE 12.1 on one of my VMs and found
the following "issues"
I worked on the packaging of PCP for openSUSE 12.1, so am to blame for
these issues.
I've raised separate bugs for the spec file issues:
https://bugzilla.novell.com/show_bug.cgi?id=732763
Hi David,
aside from the 'obsoletes' issues, I'm just wondering about the
package split in OpenSuSE: is the libXXX package naming for libs
a hard and fast rule for SuSE based distros? The alternative, as we
have already done for Fedora and derivatives, is to split the libs
off into pcp-libs and pcp-libs-devel. This is to for "multilibs",
to allow 32 and 64 bit packages to be installed on the same system
for those arch that support it (e.g. i686 and x86_64). See
http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks#Splitting_libraries_into_separate_packages
Could we unify the SuSE and Fedora versions of the RPM spec? The
latest Fedora spec is here:
ftp://oss.sgi.com/projects/pcp/download/rpm/Latest/pcp.spec
Also, Fedora-15 and later use systemd, but don't have the same
issues that Ken reported with legacy init script output being
redirected to systemctl and then onto syslog by default. I guess
systemd and systemctl on SuSE must have different default settings
somewhere ..?
Cheers
-- Mark
|