From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111781 invoked by alias); 14 Oct 2019 08:55:14 -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 111765 invoked by uid 89); 14 Oct 2019 08:55:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1125, HX-HELO:sk:mail-ed, H*r:sk:mail-ed, HX-Spam-Relays-External:sk:mail-ed X-HELO: mail-ed1-f54.google.com Received: from mail-ed1-f54.google.com (HELO mail-ed1-f54.google.com) (209.85.208.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 14 Oct 2019 08:55:12 +0000 Received: by mail-ed1-f54.google.com with SMTP id r18so2413058eds.13 for ; Mon, 14 Oct 2019 01:55:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=lUF6zffUkqRZ1M8fhKLREED3WGtMx8qgkvUygrtpHQc=; b=JDZT8kWI/pNkKt+6ME5AApXk9KyfE2Gc8KtpkFtkgV/QK4utgY3Z8Rb1ddD9v+FDYu IBIH4/fSMKQxVrm5awHnm7lo3oLtYAXoGzW9OpeRX4u8Qfu7yYQqm38881TLgNElIgw5 DCmoL9bz3hGsspMTR5VPO53aRDrPV0HH08WWBIdCaIskNB5IdwtK/KcYrxF7bp9dArFV 9g4CYTdS6FvASJTLR2VWjTCjCEekP5E7cxl4JQX3rZIFpzcd53iZQva3iIhCS1wTpjOU QmJhYuxeQJpCWcyelhkV2drJy9lyTBGKFf7C2ME396JzyTkah/3akRVOEiwiDTIFCL9i cvVw== Return-Path: Received: from [10.0.2.15] ([46.189.77.18]) by smtp.gmail.com with ESMTPSA id c6sm2226625ejz.79.2019.10.14.01.55.09 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 14 Oct 2019 01:55:09 -0700 (PDT) Subject: Re: cygport development To: cygwin-apps@cygwin.com References: <3501279f-70c8-042c-2e60-2cd315277ae9@SystematicSw.ab.ca> <97e449ba-2c23-a110-ce95-850394b398cf@gmail.com> <871rvgwqbc.fsf@Rainer.invalid> From: Federico Kircheis Message-ID: <0d57d59b-638f-47ae-bdd0-eefda2e63f0c@gmail.com> Date: Mon, 14 Oct 2019 08:55:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <871rvgwqbc.fsf@Rainer.invalid> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-10/txt/msg00011.txt.bz2 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.