DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=IiUH6V0sHpSeENIX
	tdqGkiLTuJ9DkcNMvtihj64yvXreJrE8Wrpkm4+44bgZ9vO2BjY4wnixRc3B83YL
	gFErqZqwVsYZc6gIiJJI0KWxUiRrGa2dawQ2mz3ZPMKUGEdmsFDKieX0L8q5MsnQ
	m/yrRJ395PIqP14tP7kp5G+RMb0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-to: cygwin AT cygwin DOT com
Subject: Re: redistributing a part of cygwin
References: <56B3592A DOT 9080400 AT unimi DOT it> <87k2mktk0b DOT fsf AT Rainer DOT invalid>
To: cygwin AT cygwin DOT com
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Message-id: <56B412BE.1060708@cygwin.com>
Date: Thu, 04 Feb 2016 22:10:54 -0500
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-version: 1.0
In-reply-to: <87k2mktk0b.fsf@Rainer.invalid>
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: 7bit

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