Hi, Mark -
> >(Note that there is no C++ in the third-party programs. They are
> >just dead data files - web assets - and they are not build- or
> >install-dependencies of PCP / pmwebd. They just complete the user
> >experience.)
>
> OK, so poking around a bit further around the largest of the
> embedded javascript files: jquery-1.7.2.js and jquery-ui-1.10.2.js
> [...]
> BUT I don't see this in Fedora (and presumably other distros) and
> to my eyes therein lies the root of the problem - pcp-webapi should just
> have a dependency on jquery-noarch or some such package. [...]
Formal web application asset packaging is a relatively newfangled
phenomenon in OS-distro land. It's because they tend to be
packaged/distributed as monolithic units with plenty of bundling, as
indeed you noticed in the case of jquery. This is not new at all: it
is a different world where bundling is for now the norm.
There is some gradual progress in OS-level formal packaging [1], but
it's not a mature concept. Web apps don't have the sort of dynamic
linking or fixed-ABI infrastructure to let e.g. parts be upgraded
separately.
[1] http://fedoraproject.org/wiki/Packaging:Web_Assets
> [...] I haven't looked any further, but graphite-web.noarch kind of
> sounds promising .. can't we just dep that?
To some extent, yes, but that package includes more than just the web
assets (js/png/css and such): namely python code, and system web
server conf.d extensions. Fedora sysadmins wouldn't enjoy especially
that last part.
- FChE
|