Wireshark mailing list archives
How to test legacy (glib-compat) code
From: Joerg Mayer <jmayer () loplof de>
Date: Wed, 27 Oct 2021 11:27:44 +0200
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 -- Joerg Mayer <jmayer () loplof de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___________________________________________________________________________ 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
Current thread:
- How to test legacy (glib-compat) code Joerg Mayer (Oct 27)
- Re: How to test legacy (glib-compat) code Gerald Combs (Oct 27)
- Re: How to test legacy (glib-compat) code Joerg Mayer (Oct 27)
- Re: How to test legacy (glib-compat) code John Thacker (Oct 27)
- Re: How to test legacy (glib-compat) code Gerald Combs (Oct 27)