On 13/05/11 at 10:53 +0200, Michael Below wrote: > Hi, > > reported the markdown.rb issue to Redcarpet upstream. The author > explained to me that markdown.rb is a common compatibility layer of all > Ruby Markdown implementations: > > > The point of having a `markdown.rb` (like all Markdown libraries for > > Ruby do, not only RDiscount and Redcarpet) is to allow other > > libraries to automatically use any installed Markdown library on the > > system by calling `require 'markdown'`. If you look at the Redcarpet > > source code, you'll see that the exported `Markdown` is actually > > `RedcarpetCompat` which has exactly the same API and functionality as > > RDiscount and Bluecloth. > > > > In a perfect world, every program would just require the Markdown > > library they plan to use, but this it not the case. There are already > > way too many programs that depend on this "idiom", and dropping > > `markdown.rb` would stop Redcarpet from working with them. > > Maybe this is not the case with other gems, but in case of markdown the > alternatives system would be the right way to handle this. So my second > proposal (making alternatives as a gem2deb option) would be a good way > to settle this.
It might make sense to use alternatives in that case (but do we really want to support different markdown implementations in Debian? Is there really a point?) But it's not necessary to deal with that at the gem2deb level: it can simply be dealt with in the packages affected. L. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
