| Hi,
As for the options proposed by Dario, 1) git submodules basically pins a specific commit of an external repository into your repository. It also requires additional git commands to checkout and move the ‘pin’ forward when anything is added to the external repo which is desired in the git repo. In my experience it is useful to include specific (release-)tags from external libraries, which develop on their own pace, not s much for development in parallel which is our use case. 2) git lfs could be interesting, but also makes it more complex for users, needing to install additional git features. In my experience something to be used strategically, I was a bit underwhelmed when finding 128 byte capture files stored with git lfs.
Although I’ve little experience with happy-shark, in theory I would like to see a (especially a TCP) test suite independent of Wireshark version, which is could probably best served by happy-shark.
Thanks, Jaap
Talking about your options: 1) my concern here is that we would have 2 repos, with parallel lifecycles, that are not enforced to stay aligned. A change in a dissector would benefit from a test case, but such a testcase in happy-shark would be proposed after the code merge in the main repo. That would slow down the process, wouldn't it? 2) this is the current situation. Ideal in the sense that a change carries the code and the testcase. Suboptimal because as soon as the testcases grow, the repo gets too heavy, as you said.
If the concern is not to make the repo too heavy we may investigate other options as well. 1) use git submodules 2) use git lfs Option 2 sounds promising: "Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git". We do have a dataset. Moreover gitlab.com supports LFS. Unfortunately I don't have direct experience with either submodules and lfs, hence I cannot provide more than just raw ideas.
--
___________________________________________________________________________ Sent via: Wireshark-dev mailing list < wireshark-dev@xxxxxxxxxxxxx> Archives: https://www.wireshark.org/lists/wireshark-devUnsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|
