Skip to content
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

Closed
VelocityRa opened this issue Feb 10, 2023 · 7 comments
Closed

Request to indefinitely keep previous versions for pre-releases #19

VelocityRa opened this issue Feb 10, 2023 · 7 comments
Assignees
Labels

Comments

@VelocityRa
Copy link

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?

@joachimmetz
Copy link
Member

joachimmetz commented Feb 10, 2023

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 make dist was made for.

Forth it sounds to me like a very fragile distribution process if it cannot account for newer versions or versions going away (being deprecated)

@joachimmetz joachimmetz changed the title Deletion of previous releases Request to indefinite keep previous versions for pre-releases Feb 10, 2023
@VelocityRa VelocityRa changed the title Request to indefinite keep previous versions for pre-releases Request to indefinitely keep previous versions for pre-releases Feb 10, 2023
@VelocityRa
Copy link
Author

VelocityRa commented Feb 10, 2023

Third vcpkg should be able to re-create a release based on the source, this is what make dist was made for.

I see, we weren't aware of that.

Forth it sounds to me like a very fragile distribution process if it cannot account for newer versions or versions going away (being deprecated)

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?
Are releases packages available anywhere?

@VelocityRa
Copy link
Author

Or preferably, CMake integration.

@joachimmetz
Copy link
Member

I'm not sure why you use Github "Releases" only for pre-releases and not actual releases?

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.

Or preferably, CMake integration.

why does every dist platform make its short comings the problem of the upstream project?

@joachimmetz joachimmetz self-assigned this Feb 10, 2023
@VelocityRa
Copy link
Author

It's not really a problem with libqcow. Just a feature request. To support the most widely used C/C++ build system.

@joachimmetz
Copy link
Member

Just a feature request.

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.

To support the most widely used C/C++ build system.

According to who? based on what data?

@VelocityRa
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants