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

Require libcdio at least 2.0.0 #29

Merged
merged 1 commit into from
Mar 12, 2020
Merged

Require libcdio at least 2.0.0 #29

merged 1 commit into from
Mar 12, 2020

Conversation

rocky
Copy link
Collaborator

@rocky rocky commented Mar 10, 2020

I doubt 0.83 still works, although I haven't checked (and don't have much
interest in checking).

A lot has gone on since 0.83 so even if it still works, strong-arming
folks to get up to 2.0.0 is probably a good thing (from the developer
side if not the end-user side) in the long run.

And it isn't like 2.0.0 from the last day of 2017 is is all that new.

I doubt 0.83 still works, although I haven't check (and don't have much
interest in checking).

A *lot* has gone on since 0.83 so even if it still works, strong-arming
folks to get up to 2.0.0 is probably a good thing (from the developer
side if not the end-user side) in the long run.

And it isn't like 2.0.0 from the last day of 2017 isn't is all *that* new.
@rocky rocky requested review from boretom, enzo1982 and eshattow March 10, 2020 10:01
@rocky
Copy link
Collaborator Author

rocky commented Mar 10, 2020

@boretom @eshattow @enzo1982 : Your thoughts?

See also #14 (comment)

Copy link
Collaborator

@enzo1982 enzo1982 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just checked and the latest libcdio-paranoia still builds against libcdio 0.83. But nevertheless I'm all for making this change.

Many bugs have been fixed in the past years and I remember a few times where I tried to reproduce an issue just to find out that it had long been fixed, but the user's distribution still packaged an old libcdio release.

@rocky
Copy link
Collaborator Author

rocky commented Mar 10, 2020

@enzo1982 Thanks for the feedback.

I should also note that there are a number of CVE's logged for libcdio pre 2.0.0.

Copy link
Collaborator

@boretom boretom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm all for using a newer version with newer bugs :)

@rocky
Copy link
Collaborator Author

rocky commented Mar 12, 2020

Ok. Let's do it.

@rocky rocky merged commit ef4bff8 into master Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants