public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: redistributing a part of cygwin
Date: Fri, 05 Feb 2016 03:11:00 -0000	[thread overview]
Message-ID: <56B412BE.1060708@cygwin.com> (raw)
In-Reply-To: <87k2mktk0b.fsf@Rainer.invalid>

On 02/04/2016 01:20 PM, Achim Gratz wrote:
> Fabio writes:
>> we have compiled a parallel program for Windows using cygwin.
>> In order to make the program work on any computer we have to include
>> in the package some parts of cygwin (some .dll and some .exe).
>
> There's another option: providing a script or instructions on how to
> install Cygwin and avoid the whole binary distribution headache.  In
> that case you'd provide a package repository that can be added to the
> main Cygwin one during installation, in the way Cygwin Ports is doing.

Yeah, that's certainly good advice.  It makes a package out of the original 
program that Cygwin's setup understands and, as a result, the next step of
offering the program as a package to the rest of the Cygwin community
becomes very simple.  If adding the program to the Cygwin distribution
isn't acceptable or possible for any reason, just hosting it in your own
"third-party" repository, as Achim suggests, is a good alternative.  This
still uses Cygwin's setup as the program's installation mechanism and so is
completely compatible with any existing or future Cygwin installation.  It
may not be obvious but that's a big win when it comes to maintaining a
working program and any Cygwin installation.  But if that's not enough to
sway one towards working within the architecture of Cygwin's setup, another
alternative that's arguably easier to do is to use Cygwin's setup with its
command line parameters to install the needed packages.  This could be
invoked from whatever installation method the original program uses.  The
Cygwin packages installed in this way are still 100% compatible with any
current or future Cygwin installation.

Any of these choices are much better and easier to maintain than a
directory somewhere with a copy of a bunch of Cygwin DLLs and the program.
They are definitely worth considering.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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:[~2016-02-05  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 13:59 Fabio
2016-02-04 14:05 ` Tim Prince
2016-02-04 14:26 ` Marco Atzeri
2016-02-04 18:20 ` Achim Gratz
2016-02-05  3:11   ` Larry Hall (Cygwin) [this message]

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=56B412BE.1060708@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).