* AW: [ITP] Mini-XML (mxml)
@ 2018-01-09 7:07 Stefan Köpsell
2018-01-09 18:52 ` Achim Gratz
0 siblings, 1 reply; 6+ messages in thread
From: Stefan Köpsell @ 2018-01-09 7:07 UTC (permalink / raw)
To: 'Yaakov Selkowitz', cygwin-apps
Hello,
I kindly want to ask if there are any further comments and suggestions.
Thanks,
Sincerely,
Stefan
---------------------------------------------------
Hello,
thanks for your advice.
> Do you plan on ITPing something which uses this? A library by itself is of little use.
Hm, not at the moment. But several of our projects depend on the library - and it makes contributing more easy, if the library is available as Cygwin package.
>Several problems:
>* The source package (NAME) should be name mxml;
>* A shared library should be created (pass --enable-shared to cygconf);
>* Static libraries are not generally desired;
>* There should be 2-3 subpackages, mxml with any program/utilties,
>ibmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
There a now two packages: one containing the shared library and the other containing the development files
See: https://sk13.xyz:45443/cygwin/x86/
Sincerely,
Stefan
-----Ursprüngliche Nachricht-----
Von: cygwin-apps-owner@cygwin.com [mailto:cygwin-apps-owner@cygwin.com] Im Auftrag von Yaakov Selkowitz
Gesendet: Freitag, 22. Dezember 2017 21:37
An: cygwin-apps@cygwin.com
Betreff: Re: [ITP] Mini-XML (mxml)
On 2017-12-22 12:49, Stefan Köpsell wrote:
> I am interested in becoming a package maintainer for the Mini-XML
> library (http://michaelrsweet.github.io/mxml/).
>
> Mini-XML is a small XML parsing library that you can use to read XML
> and XML-like data files in your application without requiring large
> non-standard libraries.
Do you plan on ITPing something which uses this? A library by itself is of little use.
> I have tried to make a first package and uploaded it here:
> https://sk13.xyz:45443/cygwin/x86/libmxml-dev/
>
> I would be thankful for any hints regarding issues / quality
> improvements with this package.
Several problems:
* The source package (NAME) should be name mxml;
* A shared library should be created (pass --enable-shared to cygconf);
* Static libraries are not generally desired;
* There should be 2-3 subpackages, mxml with any program/utilties,
libmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
--
Yaakov
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: AW: [ITP] Mini-XML (mxml)
2018-01-09 7:07 AW: [ITP] Mini-XML (mxml) Stefan Köpsell
@ 2018-01-09 18:52 ` Achim Gratz
2018-01-09 22:17 ` AW: " Stefan Köpsell
0 siblings, 1 reply; 6+ messages in thread
From: Achim Gratz @ 2018-01-09 18:52 UTC (permalink / raw)
To: cygwin-apps
Stefan Köpsell writes:
> I kindly want to ask if there are any further comments and suggestions.
I think the remaining question was this:
> Do you plan on ITPing something which uses this? A library by itself
> is of little use.
Which is probably something you might have an answer to…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
^ permalink raw reply [flat|nested] 6+ messages in thread
* AW: AW: [ITP] Mini-XML (mxml)
2018-01-09 18:52 ` Achim Gratz
@ 2018-01-09 22:17 ` Stefan Köpsell
2018-01-09 23:55 ` David Stacey
2018-01-10 16:34 ` Achim Gratz
0 siblings, 2 replies; 6+ messages in thread
From: Stefan Köpsell @ 2018-01-09 22:17 UTC (permalink / raw)
To: 'Achim Gratz', cygwin-apps
Hello,
Thanks.
> Do you plan on ITPing something which uses this? A library by itself
> is of little use.
The only answer I have is, that 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.
In this case I would revoke my ITP.
Sincerely,
Stefan
-----Ursprüngliche Nachricht-----
Von: cygwin-apps-owner@cygwin.com [mailto:cygwin-apps-owner@cygwin.com] Im Auftrag von Achim Gratz
Gesendet: Dienstag, 9. Januar 2018 19:52
An: cygwin-apps@cygwin.com
Betreff: Re: AW: [ITP] Mini-XML (mxml)
Stefan Köpsell writes:
> I kindly want to ask if there are any further comments and suggestions.
I think the remaining question was this:
> Do you plan on ITPing something which uses this? A library by itself
> is of little use.
Which is probably something you might have an answer to…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: AW: AW: [ITP] Mini-XML (mxml)
2018-01-09 22:17 ` AW: " Stefan Köpsell
@ 2018-01-09 23:55 ` David Stacey
2018-01-10 16:34 ` Achim Gratz
1 sibling, 0 replies; 6+ messages in thread
From: David Stacey @ 2018-01-09 23:55 UTC (permalink / raw)
To: cygwin-apps; +Cc: stefan.koepsell
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: AW: AW: [ITP] Mini-XML (mxml)
2018-01-09 22:17 ` AW: " Stefan Köpsell
2018-01-09 23:55 ` David Stacey
@ 2018-01-10 16:34 ` Achim Gratz
1 sibling, 0 replies; 6+ messages in thread
From: Achim Gratz @ 2018-01-10 16:34 UTC (permalink / raw)
To: cygwin-apps
Stefan Köpsell writes:
> The only answer I have is, that 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.
If that's the only reason, you might want to provide your own repository
that you then use together with the main Cygwin one.
> But I understand that this argument might not be very convincing.
That isn't the only factor in the decision, but since we already have a
bunch of XML libraries I'd personally ask what's wrong with those that
the new package does better. It appears that the package is in
EPEL/CentOS7 and openSUSE, so that would tip the scales somewhat in favor of
including it in Cygwin as well.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
^ permalink raw reply [flat|nested] 6+ messages in thread
* AW: [ITP] Mini-XML (mxml)
2017-12-22 20:36 ` Yaakov Selkowitz
@ 2017-12-30 13:02 ` Stefan Köpsell
0 siblings, 0 replies; 6+ messages in thread
From: Stefan Köpsell @ 2017-12-30 13:02 UTC (permalink / raw)
To: 'Yaakov Selkowitz', cygwin-apps
Hello,
thanks for your advice.
> Do you plan on ITPing something which uses this? A library by itself is of little use.
Hm, not at the moment. But several of our projects depend on the library - and it makes contributing more easy, if the library is available as Cygwin package.
>Several problems:
>* The source package (NAME) should be name mxml;
>* A shared library should be created (pass --enable-shared to cygconf);
>* Static libraries are not generally desired;
>* There should be 2-3 subpackages, mxml with any program/utilties,
>ibmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
There a now two packages: one containing the shared library and the other containing the development files
See: https://sk13.xyz:45443/cygwin/x86/
Sincerely,
Stefan
-----Ursprüngliche Nachricht-----
Von: cygwin-apps-owner@cygwin.com [mailto:cygwin-apps-owner@cygwin.com] Im Auftrag von Yaakov Selkowitz
Gesendet: Freitag, 22. Dezember 2017 21:37
An: cygwin-apps@cygwin.com
Betreff: Re: [ITP] Mini-XML (mxml)
On 2017-12-22 12:49, Stefan Köpsell wrote:
> I am interested in becoming a package maintainer for the Mini-XML
> library (http://michaelrsweet.github.io/mxml/).
>
> Mini-XML is a small XML parsing library that you can use to read XML
> and XML-like data files in your application without requiring large
> non-standard libraries.
Do you plan on ITPing something which uses this? A library by itself is of little use.
> I have tried to make a first package and uploaded it here:
> https://sk13.xyz:45443/cygwin/x86/libmxml-dev/
>
> I would be thankful for any hints regarding issues / quality
> improvements with this package.
Several problems:
* The source package (NAME) should be name mxml;
* A shared library should be created (pass --enable-shared to cygconf);
* Static libraries are not generally desired;
* There should be 2-3 subpackages, mxml with any program/utilties,
libmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
--
Yaakov
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-01-10 16:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-09 7:07 AW: [ITP] Mini-XML (mxml) 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
2018-01-10 16:34 ` Achim Gratz
[not found] <00d101d37b54$5d9b3b40$18d1b1c0$@tu-dresden.de>
2017-12-22 18:49 ` Stefan Köpsell
2017-12-22 20:36 ` Yaakov Selkowitz
2017-12-30 13:02 ` AW: " Stefan Köpsell
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).