-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to indefinitely keep previous versions for pre-releases #19
Comments
So first, I'm was not aware of this vcpkg port or the release process behind, the maintainers never contacted/consulted me Second these are pre-releases / under development, also see https://github.com/libyal/libyal/wiki, for which it is strongly recommended to keep up to date with the latest version. Third vcpkg should be able to re-create a release based on the source, this is what Forth it sounds to me like a very fragile distribution process if it cannot account for newer versions or versions going away (being deprecated) |
I see, we weren't aware of that.
Well, yeah. Especially now with vcpkg's versioning feature, it is. But we thought those release packages were what we were supposed to be using. I'm not sure why you use Github "Releases" only for pre-releases and not actual releases? |
Or preferably, CMake integration. |
Because I don't have the bandwidth to maintain releases at this point. This project is a single person best effort. People expect all kinds of additional commitments with final releases.
why does every dist platform make its short comings the problem of the upstream project? |
It's not really a problem with libqcow. Just a feature request. To support the most widely used C/C++ build system. |
So you're agree-ing that you're making this a problem of the upstream, instead of e.g. Debian apt that keeps a copy of the source distribution package.
According to who? based on what data? |
You're correct, I'm afraid I have not conducted extensive polls on the matter. Closing the issue as my initial question has been answered. |
The vcpkg port of this uses specific releases. It breaks every time you make a new release and delete everything else, so perhaps you could keep old releases around?
The text was updated successfully, but these errors were encountered: