Closed seamlik closed 4 years ago
~
is determined by the HOME
env variable falling back to the user.home
system property.
So perhaps you can configure the HOME
env var to point to a writable folder.
PS. This is a first I have heard of the user not having write access to the HOME
folder.
Setting HOME
does the trick, thanks for the tip.
However, this seems to be a good feature to me anyway. I suppose you guys can count it as a low-priority feature wish.
fakeroot
is used when building Debian package. Under this environment, root
permission is simulated but without the actual permission, and HOME
refers to /root
. That's why the process does not have access to it.
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Bnd/Bndtools or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.
Currently (3.5)
bnd
hardcodes its data directory (which is~/.bnd
). This causes some problems when we were buildingbnd
in Debian. While Gradle is preparing the project,bnd
attempts to initialize an HttpClient which places its URL cache in~/.bnd/urlcache
. In Debian's build environment, the user is simulated asroot
but without root permission, eventually Gradle fails to create the data directory and dies gloriously.Therefore, I wish
bnd
can have an option to customize the location of its data directory. I believe there are other scenarios requiring this feature.Here is a portion of the error message: