[Pkg-haskell-maintainers] Bug#724636: Could you please keep us posted on pandoc 1.12?

Jonas Smedegaard dr at jones.dk
Fri Dec 20 02:28:43 UTC 2013

Quoting Joachim Breitner (2013-12-20 00:34:48)
> Am Donnerstag, den 19.12.2013, 09:05 -0800 schrieb John MacFarlane:
> > I plan to put out a new pandoc release in the next couple weeks.  
> > I'd be happy to fix any issues that are causing problems for Debian 
> > packaging. Just explain to me clearly what those issues are (e.g. 
> > which javascript code you're talking about).
> Jonas may amend this if I miss anything, but the general idea is:
>  * Ship all files required at run time (i.e. do not rely on the
>    ability to download files when the user runs the program).
>  * Include a “source” version of all files. For Javascript, this is
>    usually the commented, unminimized version, but if it was created 
>    from a different file (e.g. compiles from a different programming 
>    language), include that source.
>  * If you include a minimized version of the script, include the
>    source, even if you download the minimized version from somewhere 
>    and would usually not bother about the source?
>  * Ideally, do any processing steps (e.g. minification) at build
>    time. If that is not feasible, verify that you really have the 
>    source for the given file (e.g. by manually doing the 
>    minification), and document the building process.
>  * Ideally use a minimizer available in Debian. yui-compressor is
>    available, node-uglify is available, the uglify-script in 
>    jquery/build is not avilable (too lazy to find out why).
> If this sound too buerocratic, then ask yourself the question “If my 
> users want to change any functionality of may package, can they do 
> that, and can they build the modified code, without external, possibly 
> non-free tools”. All the bullet points turn out to be necessary 
> conditions.

Above points are all relevant, but some are only "nice to have".

Only point really necessary is to ship the true source (the format 
preferred for editing the code) for all code shipped - e.g. the 
non-minified forms of all included javascript files.  Obviously that can 
be addressed by not shipping javascript at all, only reference online 
hosted instances of them, but see next point...

It is nice (but not necessary) if Pandoc includes and makes use of local 
files as much as possible (i.e. not e.g. mathjax as John pointed out in 
private, but e.g. Slidy which I believe is avoided in recent releases).

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-haskell-maintainers/attachments/20131220/1fafff70/attachment.sig>

More information about the Pkg-haskell-maintainers mailing list