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

LIB-28: allow using numbers as devices on Mac OS X #37

Merged
merged 4 commits into from
Sep 27, 2013

Conversation

JonnyJD
Copy link
Contributor

@JonnyJD JonnyJD commented Aug 1, 2013

This additionally accepts numbers as disc devices on Mac OS X. This number is taken to be the index (starting with 1) in the list of optical disc drives as given by drutil list.

The default for Mac is now "1", with or without a disc inserted.
Direct device names are still accepted, of course.

Tracked in http://tickets.musicbrainz.org/browse/LIB-28

This is a prerequisite for allowing drive numbers.
We explicitely call it in the platform files as mb_disc_unix_read().
This removes some "black magic" since all other unportable functions
are also implemented in the platform files.

This is also a prerequisite to accept numbers as drive names for Mac OS X,
since we need to intercept the device name before opening it.
@JonnyJD
Copy link
Contributor Author

JonnyJD commented Aug 1, 2013

This will be merged (after a review period) together with #24 and #20.

Since Mac doesn't have stable disc drive device names,
one can now additionally use drive numbers.
The default is "1" which stands for the first optical disc drive.
This should be the same numbering `drutil list` uses.
JonnyJD added a commit that referenced this pull request Sep 27, 2013
see pull request #37 and LIB-28

Conflicts:
	src/unix.h
@JonnyJD JonnyJD merged commit cf8a710 into metabrainz:master Sep 27, 2013
@JonnyJD JonnyJD deleted the mac_drive_numbers branch September 27, 2013 11:35
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.

1 participant