[Pkg-javascript-devel] Javascript trigger design

[Thomas Goirand]

On 11/29/2014 06:10 PM, Jérémy Lal wrote:
> Le vendredi 28 novembre 2014 à 20:46 +0100, Jonas Smedegaard a écrit :
>> Quoting Thorsten Glaser (2014-11-28 13:20:36)
>>> On Fri, 28 Nov 2014, Thomas Goirand wrote:
>>>
>>>> It's been a long time I've been thinking about it, and I believe that 
>>>> the only way to do this, would be to use triggers. Though I have 
>>>> never
>>
>>> Look at libjs-protoaculous which combines prototype and scriptaculous 
>>> into one (possibly minified) js file. In (our inhouse version of) 
>>> FusionForge, we just depend on it, and it contains all the trigger and 
>>> dependency magic needed for that.
>>
>> Just looking at the package name that seems not an ideal aproach: Should 
>> we then make packages for each combination of libraries to be merged 
>> together, or am I missing a more clever logic?  Or do you perhaps point 
>> at that package not suggesting duplicating it but instead cherry-picking 
>> triggers for a system-wide structure?
> 
> I suggest bundling javascript, stylesheets, images, assets in general
> should be done using a custom, per-package, makefile (or makefile
> target). Something in postinst ?
> You can't standardize upon absence of standard.
> 
> Jérémy.

That's what I'm doing already, it's just that I *also* need to do it
when a javascript package is upgraded.

Cheers,

Thomas