X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=jJjpk/ulB1UrMiyV
	EYC1VTnhyAie+LqJor+Z7N8vfPvF75uiMyylDlvNi9a5PAtCsa+UjJaGTwsjB0wl
	w7HHBrVG7IL68PGHq1We9RSZqnkT5B0Dcxb+0Xlsp1WERPMASR/EAk2S8fZDS+c+
	G4I1YwM0xblcwc2oTStC9VfrNgc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=zptJ5SGHBo3b89sp11mlAR
	nsVz0=; b=GBDj5OBkBwlVcHSVXGp9PPcCxO96WC6EdxWumxqhDenKf7/5tTgkmV
	I4/nFhe+LEIGN10fhnZ6J9q4s72LVxTFQOgCKBp4dfdtXGIjUH7fdrVon/dqJJ0D
	mYqX2WQcjoN3K4c+RQi0NRuPDUXlY6AIRhzwnDU3kC24tmstAYJj0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=3.8 required=5.0 tests=AWL,BAYES_80,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,RCVD_IN_JMF_BL,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Mon, 23 Feb 2015 21:21:42 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <1115493.20150223212142@yandex.ru>
To: Michael DePaulo <mikedep333 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Cygwin DLLs being modified somehow?
In-Reply-To: <CAMKht8jNLyA_hkAzdNvvANe5FhR0UYC=3w4t-XDwcapd5ywtUA@mail.gmail.com>
References: <CAMKht8jUmyh9==NdBHLs52CcgSXrxKTtx9m_+UJYqd+=+3vvrg AT mail DOT gmail DOT com>   <mce70e$g7q$1 AT ger DOT gmane DOT org>  <CAMKht8jNLyA_hkAzdNvvANe5FhR0UYC=3w4t-XDwcapd5ywtUA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Michael DePaulo!

> I found this too:
> http://cygwin.wikia.com/wiki/Rebaseall

> However, this leads to a another question. On the X2Go project, we
> compile nxproxy, a 3rd-party piece of software that we are now
> maintaining, against Cygwin. We also recompile Cygwin OpenSSH with an
> X2Go-compatibility patch applied and with Kerberos support disabled.

Is this really necessary? What parts of the OpenSSH need patching, and why
disabling Kerberos support?

> (We make sure to comply with the GPL.)

Noted. Though, it took several attempts to find links to a source code on your
website.
And "Download binary" links dumping visitor into a directory full of
different versions isn't speaking to your advantage.
Take example from virtualbox.org and rework your downloads page.

> So far we have just been distributing these .exe files and .dll
> files[1] in the X2Go Client directory (C:\Program Files
> (x86)\x2goclient\), which also contains regular win32 code. We do not
> run the Cygwin installer or call rebase. We use NSIS for our
> installer, and it simply copies the files.

> So my question is: Is there a better way to distribute/install these 2
> programs?
> (We want to make X2Go Client for Windows easy to install, even for
> people who have never used Cygwin. We also want to update/upgrade
> these files in between X2Go Client maintenance releases (like 4.0.3.x)
> only when there is a need to, such as a security update.)

> Also, in the absence of a doing things differently, should we just
> distribute the original .exe and .dll files from the cygwin binary
> packages?

I have a counter-question. Any objection you have to distribute your
application as part of Cygwin infrastructure?
You can still keep your NSIS installer, assuming you change it to download
appropriate setup.exe, and you could offer an option to make portable
installation from live system, knowing well that it's already rebased and
ready to work.
And Cygwin users, who also happened to be users of your app, will benefit from
NOT having to solve conflicts between multiple Cygwin1 DLL's.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 23.02.2015, <21:13>

Sorry for my terrible english...


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