From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-040.btinternet.com (mailomta4-re.btinternet.com [213.120.69.97]) by sourceware.org (Postfix) with ESMTPS id 16AF6395B079 for ; Fri, 12 Jun 2020 14:45:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 16AF6395B079 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=jon.turney@dronecode.org.uk Received: from re-prd-rgout-003.btmx-prd.synchronoss.net ([10.2.54.6]) by re-prd-fep-040.btinternet.com with ESMTP id <20200612144501.YGVW10362.re-prd-fep-040.btinternet.com@re-prd-rgout-003.btmx-prd.synchronoss.net> for ; Fri, 12 Jun 2020 15:45:01 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com X-Originating-IP: [86.141.128.212] X-OWM-Source-IP: 86.141.128.212 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgeduhedrudeiuddgkeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecunecujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepteelffegteeiudeuteehffevledvffeffeekgffhhfehvdfhgffhteehteelteeknecuffhomhgrihhnpegthihgfihinhdrtghomhenucfkphepkeeirddugedurdduvdekrddvuddvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduudejngdpihhnvghtpeekiedrudeguddruddvkedrvdduvddpmhgrihhlfhhrohhmpeeojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoegthihgfihinhdqrghpphhssegthihgfihinhdrtghomheq X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.117] (86.141.128.212) by re-prd-rgout-003.btmx-prd.synchronoss.net (5.8.340) (authenticated as jonturney@btinternet.com) id 5ED9C2FD016F6BA2 for cygwin-apps@cygwin.com; Fri, 12 Jun 2020 15:45:01 +0100 Subject: Re: Cygport user guide To: "cygwin-apps@cygwin.com" References: From: Jon Turney Message-ID: <8c378fcc-80e9-33d3-e30b-d91c3d77d343@dronecode.org.uk> Date: Fri, 12 Jun 2020 15:44:59 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2020 14:45:03 -0000 On 09/06/2020 23:49, Doug Henderson via Cygwin-apps wrote: > On Tue, 9 Jun 2020 at 09:56, marco atzeri via Cygwin-apps > wrote: >> On Tue, Jun 9, 2020 at 3:23 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote: >>> >> >> I suspect the user base is too small to justify the effort and I am afraid every >> major package needs a different approach. > > I find that I need an overview document to get me back up to speed > when I haven't used cygport for a while. The existing document, which > describes a very simple cygport file is a start, but stops way too > soon. I'd like to see a high level description of how cygport works. > If reading about some other packaging system would be helpful, I would > like to see a link to such documentation. I guess this is talking about the example in https://cygwin.com/packaging-contributors-guide.html? Yes, a few worked examples or top FAQ 'How do I do X with cygport?' would be a great addition there. Ideally as patches to https://cygwin.com/git/?p=cygwin-htdocs.git, but I realize writing raw HTML is so last millennium, so I will also accept words in an email. :) > Recently, I used cygport to automate the building of an app that I > will probably never ITA (it compiles cleanly, runs fine, but does not > actually work on Windows). I knew it used cmake, but I had to grep > through setup.ini to find the packages that had a development > dependency on cmake, and get the source packages to figure out how > their cygport files worked. (It's just a one line change, but it needs > to be the right line!). > > There is generated documentation, but it needs to be fleshed out to be > useful. Doing that, in an incremental fashion, might be a route to > make more helpful documentation. Uncharitably, that sounds like asking > one person to take on the bulk of the work. Perhaps those of us that > occasionally have to dig into the cygport code could git clone cygport > and make a personal branch to add some few words to any functions we > happen to study. Hopefully pull requests for comment only changes > should be easy to approve and merge. Yes, please.