From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) by sourceware.org (Postfix) with ESMTPS id 6DD3D383F871 for ; Tue, 9 Jun 2020 22:49:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6DD3D383F871 Received: by mail-io1-xd2e.google.com with SMTP id w18so32348iom.5 for ; Tue, 09 Jun 2020 15:49:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zmJhEFQ2Csg3kAn4WJw3MsE5B2yHM0wh5cIo3vXlRU4=; b=gYcMsZHiBtSmfiwZ0zjWwVhgdpC0xGCwoLi3ytV+jF1TVAS1uX/Kqy3AuesBoz8QdH ZevKXTk5tcj64I/ZN61sX7Jnle7LB6cxrAIrOO6d9FWWk2NypFihWhc3iqb5FUouVyUn /9EoGpu//8xbIj8H3boJ1olaNgA5s8Pevr7sQX31IqtDgp226NN917a862yoNkWpSuoh /K8IMAelPYov8Tx4HrW7+NZEamo6FsaRTmrMd7ZsgrLD4zyEc+48x7DEfCuxDmTSybqd WI3OvbPMGT6JzfCvQOC81I5EqApd2Fsdm7l7kXCNv2pLlqzOfdgQrm/kJ1GjFY0PxOgy MbVg== X-Gm-Message-State: AOAM533bprjQnHVi23JWeZr3QYkkjexFkgub0ywOK/FqYzE8Xl2O5tcf 1CWK10iL79BwrbYgz08+o1IrbpnnIQduavfuq2QM/G4TyT0= X-Google-Smtp-Source: ABdhPJxTqkmoQI5Dl8gDTXmtn3w5gQqgMXastmnDkCvocwrg7cON3rB0noWMKTKZW1x70fHWx2PtXsSH9GBXHcJdwNw= X-Received: by 2002:a6b:1785:: with SMTP id 127mr402950iox.136.1591742982705; Tue, 09 Jun 2020 15:49:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Doug Henderson Date: Tue, 9 Jun 2020 16:49:31 -0600 Message-ID: Subject: Re: Cygport user guide To: "cygwin-apps@cygwin.com" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL, HK_RANDOM_ENVFROM, HK_RANDOM_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, 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: Tue, 09 Jun 2020 22:49:44 -0000 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. 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. Thoughts? Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com