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-xmd5yjdbdmrexy1tmh2...@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 :)
