From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Cc: stefan.koepsell@tu-dresden.de
Subject: Re: AW: AW: [ITP] Mini-XML (mxml)
Date: Tue, 09 Jan 2018 23:55:00 -0000 [thread overview]
Message-ID: <452711b1-6719-a959-84bc-0fd5900eecaf@tiscali.co.uk> (raw)
In-Reply-To: <004101d38997$958e14e0$c0aa3ea0$@tu-dresden.de>
On 09/01/18 22:17, Stefan Köpsell wrote:
> I do not plan to ITPing something which uses Mini-XML -- because it seems that not so many other software packages are actually depend on it. And the ones I found in Debian do not attract me.
> But the reason I like to have the library in Cygwin is, that several of our projects depend on the library - and it makes contributing more easy, if the library is available as Cygwin package.
>
> But I understand that this argument might not be very convincing.
I don't think that the absence of another package using MiniXML should
necessarily exclude it from Cygwin. Historically, we've only required
that a package be available in at least one major Linux distro, and not
come with any non-free baggage. Besides, MiniXML has an executable
(mxmldoc) that uses the library.
I've taken a brief look at your packages. You've created two top-level
packages, each with its own source package, which isn't right. There
should be one single source package that creates 'mxml' plus two
additional sub-packages as follows:
- mxml, containing mxmldoc, its man page, 'COPYING' and 'README';
- libmxml1, containing the DLL (only); and
- libmxml-devel, containing the header files and lib.
If you want to see how to split a package into a library and devel
sub-packages, there are probably dozens of examples in Cygwin - take a
look at the Cygwin sources for 'tinyxml2' or 'pugixml' for inspiration.
These are fairly simple libraries split into sub-packages.
Hope this helps,
Dave.
next prev parent reply other threads:[~2018-01-09 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 7:07 Stefan Köpsell
2018-01-09 18:52 ` Achim Gratz
2018-01-09 22:17 ` AW: " Stefan Köpsell
2018-01-09 23:55 ` David Stacey [this message]
2018-01-10 16:34 ` Achim Gratz
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=452711b1-6719-a959-84bc-0fd5900eecaf@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin-apps@cygwin.com \
--cc=stefan.koepsell@tu-dresden.de \
/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).