Re: Bug#703188: Offer to sponsor ruby-pygments.rb
On Monday 03 March 2014 23:17:22 Per Andersson wrote:
> There is also the issue of the custom lexer for github markup from
> pygments in vendors, I can't see that this is resolved in current packaging.
>
> Since the idea is to use this for GitLab where ruby-github-markup will
> use this custom lexer IIRC, this needs to go somewhere.
For the record, newer version of jekyll also require ruby-pygments.rb. And
gitlab is not required for jekyll.
> In the current
> packaging, the bundled pygments is not used at all in favour for
> python-pygments in Debian (debian/patches/0002-...).
>
> My intention was to push this custom lexer upstream.
>
> https://github.com/tmm1/pygments.rb/pull/77
>
> Another way is of course to add this to the Debian pygments package (if
> pygments upstream won't allow custom lexers as stated in the pull request).
I guess that you meant adding gitlab stuff to python-pygments package, not
ruby-pygments.rb...
Anyway, here's the status as I understand it:
- gitlab custom lexer won't be merged in upstream ruby-pygments
- gitlab custom lexer won't be merged in upstream python-pygments
- python-pygment has some plugin mechanism (see
/usr/share/doc/python-pygments/plugins.html)
Possible solutions:
- create a package (upstream or debian) for gitlab custom lexer. In theory
python-pygment plugin can be used to load gitlab lexer in python-pygment.
- patch Debian's python-pygments to include gitlab custom lexer (without
using the plugin mechanism)
- package ruby-pygment.rb without gitlab lexer
>From a technical point of view (and for our user), the first solution is
probably the best.
But I don't have the skill and the time to implement it. Unless someone steps
up, I'm going to implement the latter solution.
All the best
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Reply to: