Pirate Praveen <prav...@onenetbeyond.org> writes: ... >> * For Debian, therefore, the source code for a file or program is the >> form which can be conveniently modified and shared; specifically, >> the form in which upstream will accept patches. > > This was never the intention of dfsg, it was always about freedoms of the > user receiving the source code. > > Our only consideration for dfsg qualification would be to see if a > user can exercise freedoms in a generally accepted way. In this case, > would some comfortable with javascript modify the code? If they are > able to modify the split files, they will be able to modify the > browserified files as well without any extra complexity.
Am I right in thinking that this change in the upstream source: https://github.com/wycats/handlebars.js/commit/08781798f564a68abee11c74e2b98272657b2a56#diff-a13581e6dfc1c61c90703da188230cbcR123 becomes this change in the ruby gem that subsequently goes into the package: https://github.com/leshill/handlebars_assets/commit/53443fa7f92c011714bd6aa5831be6074131cfca#diff-49dc26dc0a147a52074ac39c72bd99b1R2119 and if so, are you really trying to claim that these are indistinguishable as far as anyone working on the code might be concerned? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
signature.asc
Description: PGP signature
