This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: git repositories for cygwin packaging - please test
- From: Ken Brown <kbrown at cornell dot edu>
- To: "cygwin-apps at cygwin dot com" <cygwin-apps at cygwin dot com>
- Date: Mon, 5 Aug 2019 02:02:59 +0000
- Subject: Re: git repositories for cygwin packaging - please test
- Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cornell.edu;dmarc=pass action=none header.from=cornell.edu;dkim=pass header.d=cornell.edu;arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8weet2RHbt02ThoQ/5xaklzyXXv+uMhtySX37601ISY=; b=P9QWDD0+jiZvqHwvG3BUyyNrT0ltyKh/MJyBqlQ2Amzru1MocV8ZHMPSzsKRHj7KPkZ8Z3qq8cWX78/lBjvWaEO/uANPC/fGaKC4Aw15glVAjDmfVphHAmH09SrFk8oRvoVX3tGFU617tMyFGmrzVPcHoMCEhg7TzRamc21mo4CobKcY/2hUUm2aRWzFdFuKtQiRRsDN7elNoij8DOV9dWTu7syJIos3SgZdklp4BsGa6eD5nNB3u0611AqWuyAoNPlKZbyDGy/mQSLVsYJPfhw78cxB/w+z0X3Id6mG/wMd7lLBPLjxjxOOBjZgmZ3RqdkU3F9DctDa271vy0O1yQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=m+gfG16smOT0R0RLIzZXp2YhQZWpDWi83Nh3sAjGMfu5bA4ts6xR4OpZ2ntzFC+KJOMXB8FoblkZVt4xFU8SbfCBgm/C+LRvoVX8jYa7oet3VjwW4GvInUXu42OgdHUGBL0dk306s3lIKKCvMY0b+EltDxp/Sy8dRcYftgbYnhL3xV0V8TqXznjCAiiuPexwvTH12jXxY4Iv5e1HrIlkKrqLddsZbCs2Z+4RowUjFmkMwxdyi5KNK0E6LbcdFO/G/noLIQUHr0uXnG9bOWo7Q/A3DfkK2lIdSnXgmmxEgQo4sUJrsS3C7pMxvFvQx48VZI77d1aSRyJ0k2Tf8HM5Jg==
- References: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk>
On 8/4/2019 4:08 PM, Jon Turney wrote:
>
> While a number of maintainers keep their cygwin packaging under some sort of
> version control, there is currently no central collection of these repositories.
>
> To remedy this lack, using the same ssh key you use for sftp package upload,
> package maintainers can now also push to git repositories, like so:
>
> git push cygwin@cygwin.com:/git/cygwin-packages/<packagename>
>
> where <packagename> is a package name you are listed as a maintainer for in
> http://cygwin.com/cygwin-pkg-maint.
>
> These repositories are lazily created on the first push.
>
> Since it's intended that these repositories will only contain cygport scripts,
> patches, and other packaging files, and to prevent the accidental committing of
> upstream archives, pushes containing large binary files will be rejected.
>
> These repositories are viewable via gitweb at
> https://cygwin.com/git-cygwin-packages/ (URL may be subject to change), and
> should be cloneable via anonymous git/http with the URLs shown there.
>
> Please give this a test, if possible, and report any problems here.
Great idea! Thanks for doing this. I've pushed a few of my repos, and I've
cloned one of yours. So far everything works as expected.
By the way, people who want to switch to using these new repos as their upstream
can issue the following command:
git remote set-url origin cygwin@cygwin.com:/git/cygwin-packages/<packagename>
Ken