From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11990 invoked by alias); 14 Oct 2019 17:15:24 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 11917 invoked by uid 89); 14 Oct 2019 17:15:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,FROM_LOCAL_NOVOWEL,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=bonus, H*c:alternative, credit, fastest X-HELO: mail-qt1-f182.google.com Received: from mail-qt1-f182.google.com (HELO mail-qt1-f182.google.com) (209.85.160.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 14 Oct 2019 17:15:15 +0000 Received: by mail-qt1-f182.google.com with SMTP id j31so26428702qta.5 for ; Mon, 14 Oct 2019 10:15:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=lFnitaQq1YGRXts6WzBgq7mJs1iE1vcmyiwytjsF1D4=; b=JLGitgCizhsUWvq/aVPNby2eReRw2Ve7af9g30J5AEkjwdf9GaLKvDbkgZNyUU6Fl0 mxLNLVILJwjHsivlFyb7ZQy9koDYMLhl5rD/3P86TB7Q5FycrtHIgzyOcHV4voH6PMN4 oUJUm6e3LadCCY7FD4jcw7RxTr+AuZE8Tlz6errywHGIIKjq5X8W09Xxaa0jUEQ5or5P yodhAJsQBLc7NJriCwfi8ZcmAUGlZmpNE7l/EkkNlEITesscLrUAHKGukkh/oRCJM2d1 GWkoQRScxSAxsu7imT3jQ8tkgKzL5qBA4OG/xWSwpR+mkcGNXu5mplg5mDSIv7z4w9R2 9Syw== MIME-Version: 1.0 References: <3501279f-70c8-042c-2e60-2cd315277ae9@SystematicSw.ab.ca> <97e449ba-2c23-a110-ce95-850394b398cf@gmail.com> <871rvgwqbc.fsf@Rainer.invalid> <0d57d59b-638f-47ae-bdd0-eefda2e63f0c@gmail.com> In-Reply-To: <0d57d59b-638f-47ae-bdd0-eefda2e63f0c@gmail.com> From: Doug Henderson Date: Mon, 14 Oct 2019 17:15:00 -0000 Message-ID: Subject: Re: cygport development To: Cygwin Apps Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-10/txt/msg00012.txt.bz2 On Mon., Oct. 14, 2019, 02:55 Federico Kircheis, <> wrote: > On 13/10/2019 18.41, Achim Gratz wrote: > > Federico Kircheis writes: > >> I've sent the patches the 14.07.19, unfortunately I still got no answer. > > > > The cygport maintainer is rather busy with non-Cygwin related work these > > days, I suppose. Anyway, one of the questions I have is why you need > > these changes. Most build systems do not actually work when they > > encounter a path with spaces if they use make under the hood, so fixing > > cygport to grok such path locations isn't getting you much further I'd > > think. Can you explain? > > Yep. > > I've built some software in my windows home directory. > It contains a space. > I expected it to work. > > Instead of failing with a clear error message, the build process deleted > some unrelated files as it cd failed (or cd in the wrong directory, cant > remember right now). > > I believe it is unacceptable to delete unrelated data. > > Even if it stated that there is no intention to support path with > spaces, those scripts should fail fast and ideally with a clear error > message. > > I found it easier to quote the offending variables, as not only spaces > might cause issues. > When I encountered a similar problem, I added code to quote env variables that had spaces until cygport worked correctly. Then I submitted patches to this list and the maintainer so the current code works for my problem case OOB. This is the best and fastest way to get your problem fixed, and, as a bonus, get credit as a contributor to open source software. Doug >