Request: Versioning/release-tag

[EndlessEden]

could you add version/revision to the binaries and tag head branch (when you reach a satisfactory point). | version tracking is a bit difficult at the moment.

[andimik]

First of all, you are from Australia, so could you please tell us why you are interested in European DAB feeds (which you cannot receive at all)?

Have you found any feeds from your country which we could add to the readme? If yes, please share details and add a compressed file for testing.

Well, I personally don't think this is necessary to add a versioning. The major milestones have been (in the past years):

• July 11th, 2021 Sync issue fixed
• July 8th, 2021 GSE frames fixed (only for professional cards in Europe)
• Nov 22nd, 2020, BBframes (only for professional cards in Europe)
• Apr 5th, 2020 minor Makefile typo fixed
• Jul 18th, 2019 fix compilation warnings
• Mar 15th, 2019 last major update as another branch from athoik was integrated into master
• Oct, Nov and Dec 2019 dvb-ip-mpe2ts updates
• June 2018 mpe2aac and fedi2eti tools added and fixed FL field calc
• May 2018 eti2zmq update
• March 2018 ni2http update and ni2out added
• Feb 2018 na2ts added and ts2na and na2ni fix
• July 2017 small fixes and edi2eti tool added
• 2016 zeroMQ output added
• for older history please see https://github.com/piratfm/eti-tools/commits/

But if you still feel a versioning is needed, please send a pull request.

[EndlessEden]

First of all, you are from Australia, so could you please tell us why you are interested in European DAB feeds (which you cannot receive at all)?

Gladly, i am packaging on archlinux on the AUR (https://aur.archlinux.org/packages/eti-tools-git/) - Coming across this project when searching for tools for DAB+ used here in Australia. I figured it could be useful for others, even if i cannot use it myself.

Have you found any feeds from your country which we could add to the readme? If yes, please share details and add a compressed file for testing.

No, sadly. I was just attempting to add versioning to packages and seen no declaration of a version/revision number located in any of the libraries/files.

Well, I personally don't think this is necessary to add a versioning. The major milestones have been (in the past years):

Implying that date-code is sufficient, is what your saying? - i have no intention of involving myself with the project (its outside my area of understanding. I am still studying...), i just didnt wish to misrepresent versions to make a stable version of the package so it may be adopted into the archlinux packaging repository in the future if possible.