> On 2020-01-06 07:44, Adam Dinwoodie wrote:
>> On Mon, 6 Jan 2020 at 09:45, Arun Prakash Jana wrote:
>>> I noticed your response now. Somehow I didn't receive a mail when you
>>> I would have loved to contribute but I do not have access to any
>>> Windows system for personal usage. So I requested in this mailing list
>>> if someone can pick it up.
>> Cygwin packages are maintained by volunteers, generally because
>> they're maintaining packages they use themselves. If there were a
>> significant hole in the packages available that was causing problems
>> for Cygwin users, I can imagine one of the maintainers might look to
>> help, but I don't think anyone is going to take on maintaining a
>> package that we don't use personally and that we can see no particular
>> demand for.
>> For what it's worth, I took a quick look at your Cygwin installation
>> instructions. They reference a "copier" script at
>> but that's giving a 404 error for me.
Cygwin build/install instructions should always use cygport, as it is now
required for Cygwin packages, and takes care of using autotools, autoreconfig,
and other tool chains, selection between various source repo alternative
mirrors, build and runtime package dependencies, and setup requirements, with
minimal effort for maintainers.
For example, you should say:
Download and run Cygwin setup to install cygport and ... (package dependencies)
$ cygport nnn.cygport download all test install
Using cygport also standardizes package maintainer uploads to Cygwin servers for
automatic handling by calm, and sending announcements to mailing list
[hidden email] which also processes and formats the announcements
and forwards to [hidden email]. See:
SUMMARY="Internet Protocol bandwidth measuring tool"
DESCRIPTION="Internet Protocol bandwidth measuring tool
Iperf measures maximum TCP and UDP bandwidth performance, reporting bandwidth,
delay jitter, and datagram loss. It allows the tuning of various parameters and