Questions about creating a package or not

[BGINFO4X]

Thanks for your answers.

Do I need to compile it with 64 bits tools to distribute it with cygwin64 ?
Or can I compile the 32 bits version and distribute both ports
(cygwin32 and cygwin64)?

"In this king of package compiling 64 bits has no sense".

Thanks a lot.


2015-03-05 14:59 GMT+01:00 Andrew Schulman <schulman.andrew@epa.gov>:
>> Hello,
>>
>> I have compiled monit in cygwin but some of the functionalities are not aware.
>> I don't have the necessary programming experience to provide them.
>>
>> The binary is usable, and I supply the unaware features with some
>> wrapper scripts that "do same job".
>>
>> After talking with the monit company, they will not release a monit
>> release for cygwin in the near feature.
>>
>> What should I do? Create a package alerting that some of the
>> functionalities are not aware? Don't create a package? Forget it?
>
> Many free software packages have to be adjusted to be used in Cygwin.  Sometimes
> not every feature works.  This is perfectly okay.
>
> If you think the version you have works well enough to be useful, and you're
> willing to maintain it, then yes, please go ahead and package it.  You should
> start by reading https://cygwin.com/setup.html, as Marco said.
>
> Andrew
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple