public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wayne Barron <wayne@cffcs.com>
To: cygwin@cygwin.com
Subject: Re: Moving forward from cygwinports
Date: Tue, 04 Apr 2017 12:20:00 -0000	[thread overview]
Message-ID: <CAJatk5nrZm6Usxt0hBfa+qVJY=tYscOYoYmks3PaM07zHbF-Zw@mail.gmail.com> (raw)
In-Reply-To: <67f6b6d0-4d5d-2d81-4a66-cfb2d7623196@roaima.co.uk>

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 moment, just
have not done anything past the initial installation
And the installing of the packages for compiling.

Thanks.
Wayne

On Tue, Apr 4, 2017 at 6:38 AM, Chris Davies <chris@roaima.co.uk> wrote:
> 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 not (yet) been migrated into the main Cygwin
> repository?
>
> 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?
>
> Much appreciated.
> Chris
>
>
>

--
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

  reply	other threads:[~2017-04-04 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 10:39 Chris Davies
2017-04-04 12:20 ` Wayne Barron [this message]
2017-04-04 14:35   ` Chris Davies
2017-04-04 16:08 ` Yaakov Selkowitz
2017-04-04 17:59   ` Wayne Barron
     [not found]     ` <05817731-A39C-4240-A4BC-DD3DF27D9E1B@solidrocksystems.com>
2017-04-04 18:06       ` Vince Rice
2017-04-04 18:47         ` Wayne Barron
2017-04-04 18:59           ` Brian Inglis
2017-04-04 19:21             ` Wayne Barron
2017-04-04 19:33               ` Marco Atzeri
2017-04-04 19:38                 ` Wayne Barron
2017-04-04 18:56         ` Brian Inglis

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='CAJatk5nrZm6Usxt0hBfa+qVJY=tYscOYoYmks3PaM07zHbF-Zw@mail.gmail.com' \
    --to=wayne@cffcs.com \
    --cc=cygwin@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).