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

Porting to Darwin (macOS) #13

Closed
gmerlino opened this issue Jan 3, 2018 · 6 comments
Closed

Porting to Darwin (macOS) #13

gmerlino opened this issue Jan 3, 2018 · 6 comments

Comments

@gmerlino
Copy link

gmerlino commented Jan 3, 2018

Hi, any chance the tools are going to be ported for the Mac as well?

I noticed there is a fsck as (soon-to-be-merged?) PR: if it is too much effort for all the udftools package, could at least the filesystem checker be taken into consideration?

Let me try to add some perspective on the use cases.
According to this page:

https://github.com/JElchison/format-udf/wiki/fsck-tools-for-UDF

both on Linux and Mac there is currently no UDF fsck available supporting filesystem repair, so the forthcoming fsck would (possibly) cover both user bases.

@pali
Copy link
Owner

pali commented Jan 3, 2018

Hi! I'm not going to write any ports for Apple systems.

@gmerlino
Copy link
Author

gmerlino commented Jan 3, 2018

Are you going to accept PRs for such a port?

@pali
Copy link
Owner

pali commented Jan 3, 2018

Depends on how invasive it would be.

@gmerlino
Copy link
Author

gmerlino commented Jan 5, 2018

Please check my PR (for udffsck only):

https://github.com/argorain/udftools/pull/1

I hope it is not invasive (at all, possibly).

Please let me know your opinion.

Thanks again for your help.

@pali
Copy link
Owner

pali commented Jan 5, 2018

I see there tons of unused defined and entries... why they are there? Plus license of those file say they can be distributed under CDDL. So it means they cannot be included into udftools which is distributed under GPLv2+ and therefore incompatible with CDDL.

@pali
Copy link
Owner

pali commented Apr 22, 2018

Is anybody working on this? If not I will close this issue.

@pali pali closed this as completed May 3, 2018
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

No branches or pull requests

2 participants