On 05/08/2013 07:29 AM, Jérémy Lal wrote: > There are two different needs : > > 1) packaged webapp that depends on libjs-* package > > 2) user project that depends on libjs-* package. > > > For 1) your suggestion would work, but it wouldn't for 2).
Why not? I don't see what problems it causes for that scenario.
> Something that would work for 2) is user Makefile that helps
> setup symlinks or copies of the packaged files. Symlinks if the user
> wants to be able to upgrade the files along with packages upgrades,
> copies if he doesn't. In both cases it's up to a user script to
> install minified/unminified version, possibly renaming the files and so
> on.
this sounds like we would be encouraging a maintenance nightmare. what
if the user adds a new script or a new symlink manually to the same
directory, and then re-runs the makefile hook to bring the external
dependencies "up to date" or to switch from minified to non-minified?
for people who deploy their code from (signed) tags in a VCS, do they
have to have a new tag at each deployment that re-runs this hook to
adjust the links, thereby diverging from their VCS checkout?
> But if the user has to install libjs-jquery or libjs-jquery-minified
> each time, it is a painful process.
why is this painful? During development, you install libjs-jquery
alongside whatever other development tools, libraries, frameworks your
user project depends on. your user project links to the
/usr/share/javascript/jquery directory, whose contents are provided by
libjs-jquery.
In deployment, the sysadmins install libjs-jquery-minified on the live
server instead. this installs minified files in
/usr/share/javascript/jquery . the user project does not change at all.
Regards,
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
