❦ 12 mars 2014 21:11 CET, Philipp Kern <phil@philkern.de> :
> how bad would it be for those upstreams to just include an unused copy
> of the non-minified version? Clearly it'd never be used by anything in
> the upstream packaging because you almost always want to ship minified
> JS to browsers in production. But if they already fetch the min and
> you have a working relationship with upstream… maybe they're
> sympathetic.
It will just go out of sync. For upstream, the preferred form of
"modification" is the minified version (modification is merely the
update to a new version).
The javascript world is difficult to deal with. They like embedded
copies, they may not really care about API/ABI stability, even for big
projects. Those are difficulties that we already have to deal with. We
already work around them by using Debian package when possible but this
makes the software we ship more buggy because we don't match the exact
version that upstream uses.
We have so many important difficulties to deal with when packaging
something that uses javascript stuff that it is quite exhausting to pile
additional problems like repacking to remove unused minified JS stuff.
--
Don't comment bad code - rewrite it.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature