From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-049.btinternet.com (mailomta2-re.btinternet.com [213.120.69.95]) by sourceware.org (Postfix) with ESMTPS id 1800A3857008 for ; Sun, 25 Oct 2020 16:09:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1800A3857008 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-004.btmx-prd.synchronoss.net ([10.2.54.7]) by re-prd-fep-049.btinternet.com with ESMTP id <20201025160902.NVKC31866.re-prd-fep-049.btinternet.com@re-prd-rgout-004.btmx-prd.synchronoss.net> for ; Sun, 25 Oct 2020 16:09:02 +0000 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com X-SNCR-Rigid: 5ED9C50617690554 X-Originating-IP: [86.140.194.67] X-OWM-Source-IP: 86.140.194.67 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedujedrkeeggdekiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedtudenucenucfjughrpefufhfhvffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeevudeuiefghedvteduveeigfevjeegleeivdffudffieekudeuvdeguddvhedvgeenucffohhmrghinheptgihghifihhnrdgtohhmnecukfhppeekiedrudegtddrudelgedrieejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduuddungdpihhnvghtpeekiedrudegtddrudelgedrieejpdhmrghilhhfrhhomhepoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqecuuefqffgjpeekuefkvffokffogfdprhgtphhtthhopeeotgihghifihhnqdgrphhpshestgihghifihhnrdgtohhmqe X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.111] (86.140.194.67) by re-prd-rgout-004.btmx-prd.synchronoss.net (5.8.340) (authenticated as jonturney@btinternet.com) id 5ED9C50617690554 for cygwin-apps@cygwin.com; Sun, 25 Oct 2020 16:09:02 +0000 Subject: Re: How to create am initial cygwin package git repo? References: <43859b56a2e3cdfca6667da718956c24@xs4all.nl> <8fbe5cf1b6f455d5437cc216016ffb2c@xs4all.nl> <87lfg37m39.fsf@Rainer.invalid> From: Jon Turney To: "cygwin-apps@cygwin.com" Message-ID: Date: Sun, 25 Oct 2020 16:09:02 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3571.6 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, 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: Sun, 25 Oct 2020 16:09:06 -0000 On 18/10/2020 15:31, Erwin Waterlander wrote: > > Achim Gratz schreef op 2020-10-18 14:30: >> Erwin Waterlander writes: >>> The text on https://cygwin.com/packaging/repos.html is unclear. The >>> page says that the repo is lazily created on the first push. It should >>> say that you first clone it with this command: >>> >>>  git clone >>> ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org/git/cygwin-packages/packagename.git >>> >>> and then do a first push Yes, a bit of a surprise to me, and not intended, but it seems that the repo gets created on the first pull by a maintainer, as well. But this just gives you an empty repo, which you can just as easily create locally with 'git init' :) >> It shouldn't say that, because it works just as well when doing a git >> init locally (or using an existing local repo) and then pushing to the >> remote (which you also need to explicitly specify the first time you use >> it).  In fact that's the sane way to do it when you already have local >> history. I did have an idea to write something to grovel over the cygwin time machine history for a specific source package and create a repository from that, but it didn't seem really worth the effort. >> For your packages, please check >> >> https://cygwin.com/cgi-bin2/jobs.cgi >> >> and add the necessary BUILD_REQUIRES to make them build on the CI. It's >> recommended to iterate on the playground branch, which you can >> force-push to (i.e. you can throw away commits that have not worked out) >> and delete if no longer needed after having pushed the cleaned-up >> version to the master branch. > > Thanks! > This information should be in the Cygwin Package Contributor's Guide. Yeah, a patch to that would be ideal :)