public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Holger Bast <HolgerBast@gmx.de>
Subject: Re: [ITP] DocBook 5 + tools
Date: Wed, 05 Apr 2017 17:05:00 -0000	[thread overview]
Message-ID: <b42ed57d-f8ed-06f3-7efa-9e2b68d7a236@dronecode.org.uk> (raw)
In-Reply-To: <trinity-8e5c25eb-5111-4af9-a443-e1bc9e04e7b8-1490888376587@3capp-gmx-bs02>

On 30/03/2017 16:39, Holger Bast wrote:
> Hi there,
> I'm interested in maintaining DocBook 5 schemata plus some additional tools for docbook (daps and jing-trang). I've never maintained a package before, so I think the best way for me would be starting with DocBook 5. By creating the cygport file I run into some questions that I would like to address:

Thanks for doing this.

For the avoidance of doubt, what license applies to this?

> 1) docbook-5.0 installation path
> All docbook-4.x files are installed in /usr/share/xml/docbook/<xml-dtd-4.5> and so on. With DocBook 5 the distribution format changed and there is now one folder with all necessary information:
>
[...]
>
> I propose to put the hole distribution under
>
> /usr/share/xml/docbook/docbook-5.0/
>
> so everything is in one place. I also had a look at Ubuntu; they put the schema-folders (dtd, rng, schematron (renamed sch), xsd and catalog-docbook5.xml) under
>
> /usr/share/xml/docbook/schema
>
> and all documentation in their doc-structure. In my opinion, putting everything at one place would be the easiest way to work with.

I think the documentation should be under /usr/share/doc, both to 
conform with our packaging guidelines (such as they are), and for 
discoverability (people may know to look in /usr/share/doc for 
documentation)

  parent reply	other threads:[~2017-04-05 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 15:39 Holger Bast
2017-03-31  9:37 ` Aw: " Holger Bast
2017-04-05 17:05 ` Jon Turney [this message]
2017-04-05 19:12   ` Holger Bast
2017-04-07 10:14   ` Holger Bast
2017-04-18 14:05     ` [ITP] DocBook 5 + tools -- Next Steps? Holger Bast
2017-04-19 16:16       ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b42ed57d-f8ed-06f3-7efa-9e2b68d7a236@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=HolgerBast@gmx.de \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).