breautek commented on issue #588:
URL: https://github.com/apache/cordova-cli/issues/588#issuecomment-1322199347
If I understand it correctly, in you're environment you effectively have
`umask` set to something restrictive, like read-only, so when cordova creates a
new directory, by default it only has readonly permissions. Is that correct?
I think we could probably check and attempt to ensure that the directory
permissions it creates have write access instead of assuming, but Cordova also
relies on a lot of third-party tooling, like the Android SDK/Gradle, etc. So
I'm not sure far that will go.
For example, Gradle also fails installing the wrapper in this kind of
environment:
> * What went wrong:
Gradle could not start your build.
> Could not create service of type BuildLifecycleAwareVirtualFileSystem
using GradleUserHomeServices.createVirtualFileSystem().
> java.io.FileNotFoundException:
/home/norman/.gradle/.tmp/gradle_fs_probing9830715162890560142.tmp (Permission
denied)
So read-only filesystems is not something we can reasonably support because
third-party tooling also doesn't support this kind of environments.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
