Hi Martins,
----- Original Message -----
> Hi,
>
> I've been playing with pcp vector and grafana support just by downloaded
> the files and pointing pmwebd at those directories and the functionality
> is really impressive!
>
> Now I'm probably missing something obvious but I can't figure out how to
> build any of the pcp-webapp packages for RHEL/CentOS. I see there are
> packages here for 5:
>
> ftp://ftp.pcp.io/projects/pcp/download/rpm/pcp-3.10.4/el5/x86_64/
>
> So there must be a recipe somewhere. I'm trying to build for 6.6 and 7.
>
Currently, the only package building we do for external trees like webjs
is via fedora.spec - which is fairly limiting, and something I'd like to
start to tackle. We are seeing increasing numbers of external trees (eg
vector, webjs, parfait, pcp2pdf, pcp-cpp-pmda, ...), and a more general
solution to help build packages for those projects too would be great.
> expected. pcp-webapi builds fine. Do I need to copy the appropriate bits
> from fedora.spec into pcp.spec.in?
Hmm, you know, I think we can solve this more easily for Makepkgs builds -
how about this:
- allow people to optionally drop in certain external source tarballs in a
preset location (say, below build/tar/)
- configure.ac looks for any external source tarballs below build/tar and,
if present, these can flip switches in the build and incorporate those
external sources into the build (bit like fedora.spec does).
- add to pcp.spec.in (and debian/* builds) conditional code for the new
packges, along the lines of the @enable_python3@ guard around "python3-pcp".
- hey presto, we'd be able to have optionally built packages for any of the
external projects - and a handy generalised solution going forward I think.
cheers.
--
Nathan
|