public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] Cgreen v1.0.0
Date: Wed, 18 May 2016 16:16:00 -0000	[thread overview]
Message-ID: <ebeac38b-8c9b-a676-8e94-f5f959fda37c@gmail.com> (raw)
In-Reply-To: <573C6618.7080600@junovagen.se>

On 18/05/2016 14:54, Thomas Nilsson wrote:
> Marco Atzeri skrev:
>>
>>
>> On 18/05/2016 14:41, Thomas Nilsson wrote:
>>> Hi!
>>>
>>> I'm interested in maintaining the cygwin port of Cgreen, a modern unit
>>> testing and mocking framework for C and C++. I am one of the committers
>>> on that project and have used Cygwin as one of my major development
>>> platforms for many years and wanted to give something back.
>>>
>>> Cgreen is on GitHub. We've just released v1.0.0 and have yet to port to
>>> any major platforms although it has continuously been tested on various
>>> Linuxen, Darwin and Cygwin, of course.
>>>
>>> Cgreen is distributed under ICS license ("Open BSD").
>>>
>>> setup.hint part of cgreen.cygport:
>>> --------------------------------------------
>>> # setup.hint generation
>>> CATEGORY="Devel Utils Libs"
>>>
>>> SUMMARY="A modern C and C++ unit testing and mocking framework"
>>>
>>> DESCRIPTION="A modern C and C++ unit testing and mocking
>>> framework. Cgreen uses a fluent API for asserts and constraints
>>> which makes writing concise unit tests a breeze. Output for failing
>>> asserts are clear and descriptive. The optional runner will
>>> automatically find all your tests without you having to remember to
>>> add them to the test suite. All in all, awesome for TDD-ing."
>>> -----------------------------------------
>>>
>>> Regards,
>>> Thomas
>>>
>>> PS. I've followed the section "Submitting a new package" from this guide
>>> when sending this. I hope that it is up-to-date, otherwise comment or
>>> ask. DS.
>>
>>
>> we are supposed to review the package (source and binary),
>> can you provide a link ?
>>
>>
>
> The guide at https://cygwin.com/setup.html#submitting was not clear if
> the voting needs to be before submitting or not.
>
> Ok, I'll provide a link as soon as I've uploaded them somewhere.
>
> Thanks,
>     Thomas


on the mailing list please.

I missed the point that it was NOT already available in any major
linux distro,

  parent reply	other threads:[~2016-05-18 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 12:41 Thomas Nilsson
2016-05-18 12:49 ` Marco Atzeri
     [not found]   ` <573C6618.7080600@junovagen.se>
2016-05-18 16:16     ` Marco Atzeri [this message]
2016-05-18 18:34       ` Thomas Nilsson

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=ebeac38b-8c9b-a676-8e94-f5f959fda37c@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).