From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) by sourceware.org (Postfix) with ESMTPS id 8F6993857C7F for ; Wed, 16 Dec 2020 21:44:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8F6993857C7F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dinwoodie.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=adam@dinwoodie.org Received: by mail-qv1-xf35.google.com with SMTP id a13so12293104qvv.0 for ; Wed, 16 Dec 2020 13:44:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dinwoodie.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=FOCwMvM4soBFCpfZnM/6Qs/bxB+lB9ExdvOwGELhvTM=; b=UvWM9jfHMzPkJgA6dduDlqO6HeRjkmjLr1lJstP7INaTMtEbvfulQvTvXdEo/c7vVG 8bkgN12X6kpmCZemHx2qekDIR5R0XyQgwLs60OSTk2osS7Eri8w0+mO9Fwkj5sz81z+t AJnR8t+/enzDYCSyxx86Tf49kSo3AgJfwyF60= 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:cc:content-transfer-encoding; bh=FOCwMvM4soBFCpfZnM/6Qs/bxB+lB9ExdvOwGELhvTM=; b=OEwYH2K9kwpPKZSjbbf1VwwEz9ox50XRXb/YKaRx1UtKMQIV25cCMhxXtklpdMewAi rNlYs9eb4qHvddI6Twqo43H5pmGCOSog4G6Y5zQtrB1smRb8mhpIw/2f5GlFiB6nelk6 ScA9O8ydb9AMQo9+OxpNopSpIYmQsEC80URazpNFsm6VebtuM86mCZ3NceTxUQLRW4jX gxOCapEGETTg9d5eamcbDOIkqz6FV0Au5UH0vFPT8QiTwE35z4jYd76hDyWLqJ0T3gZK 5396Iyct91h26PmLJ9YUr2h0jpyG3e2O8l46ulVvJSHqvn9CzJlCUGlCeR93RLNqDTpN 4sPQ== X-Gm-Message-State: AOAM532A8qr4W02JxX0RIkXFqwvTxBqeMGCKAttOpzaOt3N5GtqXDEBH nsCRy65UFFBbA4eweMv3jTGmB4xA/nXRqAoD4KiFCA== X-Google-Smtp-Source: ABdhPJwVJfKFE9RhjEJRAfjp2WbdoEvFveH90ENboyDnyZhwQiDenFTKlNOyRprXLq4EYOi2QpuCqjeQlxWzOvE321Q= X-Received: by 2002:ad4:5bcd:: with SMTP id t13mr45207176qvt.7.1608155099048; Wed, 16 Dec 2020 13:44:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adam Dinwoodie Date: Wed, 16 Dec 2020 21:44:23 +0000 Message-ID: Subject: Re: Finding cygport/cygwin source repositories not listed at https://cygwin.org/packages/package_list.html To: Hamish McIntyre-Bhatty Cc: Cygwin General Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 21:45:01 -0000 On Wed, 16 Dec 2020 at 20:31, Hamish McIntyre-Bhatty wrote: > I have several packages I need the Cygwin source repositories for, but > there is no link from https://cygwin.org/packages/package_list.html to > the cygwin source. > > In a few cases the repositories are also out of date (mostly Python > stuff, probably your packages adopted from Yaakov, Marco Atzeri?). > > I was wondering if there's a good way to find these/if someone might > know of the top of their head if I list them? > > It's quite a lot of packages, so it's likely better if I can be given > pointers. > > Full disclaimer: I specifically need the source repos and not just the > source packages because I'm using them for an automated source bundling > tool for my DDRescue-GUI Windows bundle (which is open source but > commercial). I've spent ages writing the script and I'd rather not do it > over again / make lots of modifications and break it. > > Any ideas? Yes, but I don't think you'll like it: use the source packages, not the repositories. There's no obligation or expectation that package maintainers make their source code available in any way other than through providing a source package. Some do provide a public repository and make it readily available, but I would not be at all surprised if some maintainers =E2=80=93 particularly for packages that don'= t get many upstream updates =E2=80=93 don't use version control at all. Further, remember for GPL-like licenses you need to provide *all* the source code that's used to create the binaries you're distributing, including both the upstream source code and any Cygwin-specific patches or modifications. Those will normally be in two separate repositories, and there's no guarantee it'll be easy to find one from the other. Taking Git as an easy example, since it's a package I maintain and am familiar with: you'd need to find both https://github.com/me-and/Cygwin-Git/ and https://git.kernel.org/pub/scm/git/git.git if you wanted the underlying repositories, and I can't think of any way to get from one to the other that's not incredibly fragile. And, as I say, I suspect there are a bunch of packages in Cygwin where it's much more difficult, if not impossible. I think a much better route here would be to parse the setup.ini files (e.g. https://mirrorservice.org/sites/sourceware.org/pub/cygwin/x86_64/setu= p.ini) to work out the paths of the source packages that correspond to each of the release packages you're using, and to use those. That's going to be less work and also less fragile than trying to hunt down repositories that may not even exist. Adam