Hi -
>> I am unconvinced that re-embedding is needed.
>
> Understood, and I tend to agree for this lib - IMO the older version could've
> been made to work as well [...]
Well, not just that. The autoconf mechanisms in place to adapt to the
presence or absence of suitable libmicrohttpd are exactly intended to
make the pcp package as a whole build even if a prereqs for one
optional part are missing. If something's wrong with the autoconf
machinery, or the Makepkgs / .dsc/.spec generation, those should be
noted as bugs.
> Yep, but note the proposed web frontend changes introduce (embed)
> three other packages also (graphite, grafana, jquery) and it appears
> that not doing so is intractable.
That's for a different reason. At this time, there appears to exist
no widespread UNIXy infrastructure to package web application
artifacts as reusable elements, so there's no way to link to a
"system" copy of these.
> Since this embedding approach is one that Frank is keen on pursuing
> (and its his prerogative),
With respect to libmicrohttpd, I am not keen on pursuing this
embedding approach, and as outlined above, the web application
artifacts are only reluctantly embedded. No "keen pursuit" here.
> I'm looking into git techniques for extracting and moving all of
> this code forward, just outside of the core PCP source tree.
The embedding issue would be an unfortunate choice of rationale for this.
- FChE
|