8000 Preserve original file information by rubensa · Pull Request #189 · angelozerr/typescript.java · GitHub
[go: up one dir, main page]

Skip to content

Preserve original file information #189

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

Merged
merged 1 commit into from
Jul 7, 2017
Merged

Conversation

rubensa
Copy link
Contributor
@rubensa rubensa commented Jul 7, 2017

Looking for "bin" folder seems a bit "tricky" to me...
For tar files we should keep original executable permissions as this info is available.
For zip files executable information could be available for UNIX systems but in current ZipEntry implementation that info seems to be not available.

Looking for "bin" folder seems a bit "tricky" to me...
For tar files we should keep original executable permissions as this info is available.
For zip files executable information could be available for UNIX systems but in current ZipEntry implementation that info seems to be not available.
if ((mode & 00100) > 0) {
// Preserve execute permissions
extractedFile.setExecutable(true, (mode & 00001) == 0);
}
break;
case TarEntry.LINK:
File linkFile = new File(destination, outFilename);
Copy link
Owner

Choose a reason for hiding this comment

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

Should be done too for link, no?

Copy link
Contributor Author
@rubensa rubensa Jul 7, 2017

Choose a reason for hiding this comment

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

Not sure.
For hard links It seems that is not necessary as It should keep original (linked) file permissions.
As for symbolic links, by default, It also seems that is not necessary (I checked with node-v6.9.4-linux-x64.tar.gz and npm symlink has all permissions -777-...). Surely we could/sould do something like:
Set<PosixFilePermission> perms = PosixFilePermissions.fromString("rwxr-xr--"); FileAttribute<Set<PosixFilePermission>> attr = PosixFilePermissions.asFileAttribute(perms); Files.createSymbolicLink(symLinkFile.toPath(), symTarget, attr);
but before that, we should check that current system is POSIX and "gess" permission pattern (in the example "rwxr-xr--") from entry attributes. (I'm not sure but I think that if system is not POSIX and you try to pass those attrs an Exception is thrown).

Have you thought on using Apache Commons Compress to avoid this low level implementation?

Copy link
Owner

Choose a reason for hiding this comment

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

Ok thanks for your feedback. If it works for you, it's OK.

Have you thought on using Apache Commons Compress to avoid this low level implementation?

I would like to avoid having dependencies just to extract node.js. We will see in the future if we have so many problem, perhaps I will switch to appache commons compress.

@angelozerr angelozerr added this to the 1.3.0 milestone Jul 7, 2017
@angelozerr angelozerr merged commit 63aedc3 into angelozerr:master Jul 7, 2017
@angelozerr
Copy link
Owner

Thanks @rubensa !

@angelozerr
Copy link
Owner

@rubensa so now embed node.js works for linux, is it OK? I would like create soon a release.

@rubensa
Copy link
Contributor Author
rubensa commented Jul 7, 2017

Hello @angelozerr
I just make a clean install using http://oss.opensagres.fr/angular2-eclipse/1.3.0-SNAPSHOT/ created a new sample Angular project and now everything seem ok.

Thanks for your good work @angelozerr

@angelozerr
Copy link
Owner

Thanks a lot @rubensa for your contribution!

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.

2 participants
0