Re: Moving forward from cygwinports

2017-04-04 Thread Wayne Barron
> python programs used on cygwin.com to properly > build the setup.ini for the repository. > It can be used for local repository. > > It replaces a previous system called "upset" > > https://www.cygwin.com/ml/cygwin-apps/2016-07/msg0.html > > Regards > Marco OK, it shows it as [Keep] So, I am a

Re: Moving forward from cygwinports

2017-04-04 Thread Marco Atzeri
On 04/04/2017 21:20, Wayne Barron wrote: Category devel, or select Not Installed, and Search for cygport (and calm?) I am installing it right now. What is (Calm)? python programs used on cygwin.com to properly build the setup.ini for the repository. It can be used for local repository. It re

Re: Moving forward from cygwinports

2017-04-04 Thread Wayne Barron
> Category devel, or select Not Installed, and Search for cygport > (and calm?) > I am installing it right now. What is (Calm)? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe inf

Re: Moving forward from cygwinports

2017-04-04 Thread Brian Inglis
On 2017-04-04 12:46, Wayne Barron wrote: > Took care of that issue with the Quoted text, using GMail. So all > should be good with that now. > Thanks, Vince. For the heads up. >> Cygport is a Cygwin package, it can/should be installed from >> Cygwin's setup. > Since it is a package, I know how to

Re: Moving forward from cygwinports

2017-04-04 Thread Brian Inglis
On 2017-04-04 12:06, Vince Rice wrote: >> On Apr 4, 2017, at 12:58 PM, Wayne Barron wrote: >>> On Tue, Apr 4, 2017 at 12:08 PM, Yaakov Selkowitz wrote: On 2017-04-04 05:38, Chris Davies wrote: > As an example, my use case is Perl-DBD-Sybase from about > three weeks ago, which works bea

Re: Moving forward from cygwinports

2017-04-04 Thread Wayne Barron
Took care of that issue with the Quoted text, using GMail. So all should be good with that now. Thanks, Vince. For the heads up. > Cygport is a Cygwin package, it can/should be installed from Cygwin's setup. Since it is a package, I know how to install the packaged, which NODE would it be located

Re: Moving forward from cygwinports

2017-04-04 Thread Vince Rice
>> On Tue, Apr 4, 2017 at 12:08 PM, Yaakov Selkowitz wrote: >>> On 2017-04-04 05:38, Chris Davies wrote: As an example, my use case is Perl-DBD-Sybase from about three weeks ago, which works beautifully but is not in the main repository. Short of moving to a Linux-based platfor

Re: Moving forward from cygwinports

2017-04-04 Thread Wayne Barron
@Chris, I know that Cygwin and Cygport are not the same. I was asking if you could perhaps share information on how to properly install Cygport. I downloaded it from here. https://github.com/cygwinports/cygport In the Cygwin, it had a Windows 32 or 64-bit installer. This does not come with such.

Re: Moving forward from cygwinports

2017-04-04 Thread Yaakov Selkowitz
On 2017-04-04 05:38, Chris Davies wrote: As an example, my use case is Perl-DBD-Sybase from about three weeks ago, which works beautifully but is not in the main repository. Short of moving to a Linux-based platform I'm now not sure how to proceed. Could someone enlighten me, please? You could

Re: Moving forward from cygwinports

2017-04-04 Thread Chris Davies
On 04/04/2017 13:19, Wayne Barron wrote: > You stated: "Short of moving to a Linux=bases platform" > I take it you have the "cygwinports" > Successfully running in a Windows Environment. > Could you please share, how to set-up cygwinports in Windows? Cygwinports is not Cygwin. Cygwin is alive a

Re: Moving forward from cygwinports

2017-04-04 Thread Wayne Barron
Chris. I have a question for you. You stated: "Short of moving to a Linux=bases platform" I take it you have the "cygwinports" Successfully running in a Windows Environment. Could you please share, how to set-up cygwinports in Windows? I have Cigwin installed on my Win10 testing system at the mom

Moving forward from cygwinports

2017-04-04 Thread Chris Davies
Hello all, I have seen that cygwinports has been closed down and I understand the reasons as posted. It's been a great resource and my thanks go out to all maintainers there and here. What options do I have going forward for packages from that repository that I can confirm do work, but have