Re: docbook-xsl URL mess

Peter Eisentraut <[email protected]>
Newsgroups gmane.text.docbook.apps
Message-ID <[email protected]>
I have filed an issue: 
https://github.com/docbook/xslt10-stylesheets/issues/201

I tried implementing this, but struggled with the build system.  So it's 
just the issue for now.


On 2020-06-08 18:00, Bob Stayton wrote:
> Yes, this needs to be fixed.  I'm cleaning up pull requests and issues 
> and will be making a new release soon.  Could you please file an issue  
> on the DocBook XSL github with your recommended fix:
> 
> https://github.com/docbook/xslt10-stylesheets/
> 
> Bob Stayton
> [email protected]
> 
> On 6/8/2020 12:02 AM, Peter Eisentraut wrote:
>> In docbook-xsl 1.79.2, the system identifier was changed from
>>
>> http://docbook.sourceforge.net/release/xsl/current/...
>>
>> to
>>
>> http://cdn.docbook.org/release/xsl/current/...
>>
>> However, this was done in a backward-incompatible way.  So now, in 
>> your customization layer or build system, you have to pick one of 
>> these URLs, and users who have a different docbook-xsl version 
>> installed locally will suffer, either because the stylesheets have to 
>> be fetched from a remote server, or the build will fail entirely.
>>
>> This didn't use to be a real problem in practice because 1.79.2 saw 
>> very little adoption, but it's now trickling into various 
>> distributions and packagings, and it's becoming a real source of 
>> frequent build problems.
>>
>> This should be fixed by making the supplied catalog files include 
>> backward-compatible mappings.  However, it seems after 1.79.2, 
>> docbook-xsl went unmaintained, so we are now stuck in this limbo.
>>
>> Is anybody in a position to get this fixed and get a new patch release 
>> out soon please?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.