Re: Bug#703188: Test issues with ruby-pygments.rb
Just to make sure, everyone is aware that GitLab no longer includes
Pygments? We switched to Highlight.js in 6.6
https://gitlab.com/gitlab-org/gitlab-ce/blob/8cc5e85543b0a553536ebe70f01fa29e0b0f60bd/CHANGELOG#L80
On Thu, Apr 3, 2014 at 4:53 PM, Dominique Dumont <dod@debian.org> wrote:
> On Thursday 03 April 2014 00:28:46 Per Andersson wrote:
>> I have created a fix and forwarded it for upstream inclusion
>>
>> https://github.com/tmm1/pygments.rb/pull/119
>>
>> When this is accepted upstream I intend to go forth with repackaging
>> the upstream tarball and removing the vendor directory entirely.
>
> Hmm, looks like this pb revolves around the adaptation done upstream to cope
> with Debian idiosyncrasies.
>
> Instead of pushing upstream to cope with Debian, I'd rather let upstream keep
> thing simple (and portable). Then as Debian packager, I would create patches
> to adapt upstream to Debian.
>
> For instance, here's what I've done with Config::Model (as upstream) and
> libconfig-model-perl (as packager):
> * Upstream cme program begins with '#!/usr/bin/env perl'.
> * This line is patched during packaging so Debian's version of cme begins with
> '#!/usr/bin/perl'.
>
> Hope this helps
>
> --
> https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
> http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
>
>
> --
> To UNSUBSCRIBE, email to debian-ruby-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 6752323.pD64sYRzgg@ylum">https://lists.debian.org/[🔎] 6752323.pD64sYRzgg@ylum
>
Reply to: