You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As someone that's dealt with such company policies in the past, often you can workaround those by simply specifying the exact "commit ID" as the tag in question for paperwork purposes. Every single commit is, in effect, a unique tag into the repository.
Otherwise 'header only' libraries often don't have explicit versions and the like, because they're meant to be integrated into other codebases not simply referenced as external libraries where versioning systems would be appropriate.
So this is also company policies being at a fundamental disconnect from some areas of FOSS, and to be frank... unless they're paying the dev for such scutwork paper-pushing concerns it's not their responsibility. :)
Perhaps they are thinking that tag / version represents an official release version of the code. That suggests it is more reliable. From this point of view, although we are a header only library, tagging makes sense. :)
Because some company policies require that open source software used must have a tag.
I also hope you create a tag for the latest location of minimp4 (https://github.com/lieff/minimp4/)
Thank you very much!
The text was updated successfully, but these errors were encountered: