Re: How to test legacy (glib-compat) code

[Gerald Combs <gerald () wireshark org>]

The oldest version of GLib that we build with is 2.56.1 on the CentOS 7 builder:

CentOS 7       2.56.1
CentOS 8       2.56.4
Debian         2.66.8
Fedora         2.68.4
macOS ARM      2.68.4
macOS Intel    2.58.3
openSUSE 15.2  2.62.6
Ubuntu         2.64.6
Win32          2.66.4
Win64          2.66.4

Is there any reason we shouldn't increase the minimum GLib version to 2.56 in the master and 3.6 branches? That would mean that we no 
longer support RHEL 6, but it's currently in "extended life cycle support": 
https://access.redhat.com/support/policy/updates/errata

On 10/27/21 2:27 AM, Joerg Mayer wrote:
> Hello,
>
> I've created a merge request (https://gitlab.com/wireshark/wireshark/-/merge_requests/4820)
> that requires a newer version (2.56) of glib than the minimum we require in cmake (2.38), so
> I created a glib-compat entry to emulate the required functionality via an older function that
> has been deprecated (2.62)
>
> Two questions:
> 1) Is any of our buildbots running on such an old version of glib so I know that it compiles?
> 2) Is there a way to test whether the compat code (text2pcap) actually works? I have no problem
>     to provide/commit a testfile.
>
> Thanks!
>     Jörg

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request () wireshark org?subject=unsubscribe