pcp
[Top] [All Lists]

Re: pcp updates: qa, docs, fixes

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: pcp updates: qa, docs, fixes
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 13 Apr 2015 03:04:17 -0400 (EDT)
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <y0mk2xk566h.fsf@xxxxxxxx>
References: <765204112.14979385.1428575388121.JavaMail.zimbra@xxxxxxxxxx> <y0mk2xk566h.fsf@xxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: LWL4Bv4sjamkJBY8y3g+et+KbM+vOQ==
Thread-topic: pcp updates: qa, docs, fixes

----- Original Message -----
> > [...] it would probably be better if pcp-webjs's %files
> just included
> 
> %dir /usr/share/pcp/webapps
> 
> (whether or not that duplicates pcp-webapi).  That way, the webjs
> stuff is not forced to match to any particular version of pcp, as
> technically indeed it does not need to.

Michael Schwendt pointed out (over in RHBZ 1204467) that there is
actually a dependency on pcp, and in this particular case, on both
the base pcp and the pcp-webapi packages - he provided this link:

https://fedoraproject.org/wiki/Packaging:UnownedDirectories

So, /usr/share/pcp comes from package "pcp" and /usr/share/pcp/webapps
comes from package "pcp-webapi".  Hence we need to depend on a version
of pcp-webapi that we know provides that directory, and there's a dep
(via pcp-webapi) on a pcp version that provides the base directory.

$ rpm -qlp pcp-webapi-3.10.1-1.fc20.x86_64.rpm | grep webapps$
/usr/share/pcp/webapps
$ rpm -qlp pcp-3.10.1-1.fc20.x86_64.rpm | grep share/pcp$
/usr/share/pcp

>  So people fond of older
> or newer webjs can install it without fretting about core pcp.

That'd break the above Fedora packaging requirement, recently fixed.

> (Similarly, the "pcp-libs = %{version}-%{release}" explicit
> dependencies should be dropped throughout the .spec file, relying
> instead on rpm's solib/soname analysis magic.)

This has come up before - the issue is rpmdiff reports problems if
this explicit versioned dependency is removed.  If that has now been
verified as resolved, then yep, send through a patch to remove 'em.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>