On Mon, Aug 12, 2013 at 1:05 PM, Robert Marcano
On 08/12/2013 03:23 PM, Robert Marcano wrote:
> want to be compatible with others distribution that have the legacy idea
Sorry, I missed this:
and the Feature says:
"Additionally the following symlinks will be provided:
out of sync that it is difficult to understand what will go to each place
So one possible option that would address your concerns would be to
require every js-foo package to also provide a webjs-foo subpackage or
so that just contains a symlink in /usr/share/web-assets/js to the
That would provide a way for dependent packages to express "hey, I
just need you on the server-side" and another way to say "hey, I need
you served over HTTP".
But then, what do we want to do about fonts? Adding *-webfonts
subpackages to every font package would be a lot of work, and makes
that awesome WordPress usecase I mentioned much, much harder. What
about CSS? Do we really need a css-bootstrap for when someone wants
to create a locally run HTML5 application with something like
node-webkit and another webcss-bootstrap for when they really want it
served over HTTP?
It's really a lot of work optimizing for what is an edge case. I'm
not convinced it's necessary, but I'll mention this to FPC during my
meeting with them on Thursday for their input anyway.