[ITA] wxWidgets3.0

[Brian Inglis]

On 2020-10-21 07:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 19/10/2020 16:31, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 17/10/2020 16:04, Brian Inglis wrote:
>>> On 2020-10-17 07:17, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>> On 17/10/2020 01:21, Lemures Lemniscati via Cygwin-apps wrote:
>>>>> On Fri, 16 Oct 2020 20:20:53 +0100, Hamish McIntyre-Bhatty via Cygwin-apps
>>>>>> Just sending this out so I can update wxWidgets to 3.0.5.1. I've pulled
>>>>>> in new patches from Fedora, but I can't find
>>>>>> mirror://portage/x11-libs/wxGTK/files/wxGTK-3.0.3-collision.patch
>>>>>> anywhere. Does anyone happen to have a copy of this?
>>>>>>
>>>>>> My hope is that it is no longer needed, but obviously I can't confirm
>>>>>> that without actually having the patch. I haven't got any files uploaded
>>>>>> yet because I'm doing a test build. If anyone has a copy of that
>>>>>> patch/knows where to find it please let me know.
>>>>> You can get them from one of the current src packages.
>>>>> List of src files: https://www.cygwin.com/packages/x86_64/wxWidgets3.0-src/wxWidgets3.0-3.0.4-1-src
>>>>> Package: http://mirrors.kernel.org/sourceware/cygwin/x86_64/release/wxWidgets3.0/
>>>> Excellent, thanks :)
>>>>
>>>> I'll post again when I've got builds and have improved the cygport file
>>>> (this one doesn't have build dependencies).
>>>>
>>>> It takes about 3-4 hours per build, somehow, so it might be a little
>>>> while, but we'll see :)
>>> Those mirrors should be part of cygport SRC_URI or PATCH_URI and will be
>>> retrieved on download.
>>>
>>> Portage is gentoo equivalent on which cygport is based and that patch hits some
>>> make and bake file and translation sources as part of a patchset series:
>>>
>>> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e16e67f0678b264a04e96954a4593ddac3a9a32d
>>>
>>> including also:
>>>
>>> https://dev.gentoo.org/~leio/distfiles/wxGTK-3.0.3_p20180104.tar.xz
>>>
>>> where you will have to figure out if you need to doenload and apply patches to
>>> their sources or make a similar change to get the equivalent effect in your
>>> cygport.
>>>
>> Thanks Brian, I'll look into those.
>>
>> It gave a 404 trying to download that patch, but not a problem because I
>> have it now. I'll look around and see if I can use those other ones you
>> sent, or if there are more patches in any more current Gentoo package.
>>
>> Hamish
> 
> Okay, new patches reviewed and BUILD_DEPENDS is sorted.
> 
> I've heard a new CI tool mentioned here (AppVeyor?). Is there a way I
> can use that to test my packaging/build-depends once this local build is
> finished?

https://cygwin.com/pipermail/cygwin-apps/2020-October/040577.html

As you adopted the package, you will first have to do a clone in your Cygwin
cygport directory from:

https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/wxWidgets3.0.git

YMMV, but after cloning adopted packages, as I have a Cygwin ssh alias defined,
I setup my .git/config for each package like:

$ tail +0 .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
        ignorecase = true
[remote "origin"]
        url = ssh://cygwin/git/cygwin-packages/curl.git
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = ssh://cygwin/git/cygwin-packages/curl
        merge = refs/heads/master

and run ssh-agent and ssh-add to provide my passphrase for uploads and pushes.
I believe you may use e.g. ssh://cygwin@cygwin.com/... instead.

If you are the original ITP packager, you have to init the package, set the
[remote "origin"], add and commit the cygport and any other files you want to
publish, then push to create the Cygwin repo.

I should now add [branch "playground"] entries to make testing appveyor CI
builds cleaner and easier, as I usually don't do this stuff enough to remember
how to do it, so I muddle through, and then forget what I need to add to my
notes on packaging.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]