)]}'
{"doc/source/developer/developing_elements.rst":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"b9871a066c6ce776202cc8deee48db70173fc936","unresolved":false,"context_lines":[{"line_number":98,"context_line":"  * outputs: None"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  Contents placed under ``$TMP_HOOKS_PATH`` will be available at"},{"line_number":101,"context_line":"  ``/tmp/in_target.d`` inside the chroot."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"``pre-install.d``"},{"line_number":104,"context_line":"  Run code in the chroot before customisation or packages are installed. A good"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_7bc5493c","line":101,"updated":"2018-07-09 06:00:48.000000000","message":"Well, the whole point of it being $TMP_HOOKS_PATH is that you should probably use the variable to find out where it is, rather than assume?  Where is that not working?","commit_id":"33756305fcccca7cd4247dfbf246792d8c294314"},{"author":{"_account_id":14727,"name":"Elyézer Mendes Rezende","email":"elyezermr@gmail.com","username":"elyezer"},"change_message_id":"7879e94d0c0d0849dfa1678ae50751b841aa482e","unresolved":false,"context_lines":[{"line_number":98,"context_line":"  * outputs: None"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  Contents placed under ``$TMP_HOOKS_PATH`` will be available at"},{"line_number":101,"context_line":"  ``/tmp/in_target.d`` inside the chroot."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"``pre-install.d``"},{"line_number":104,"context_line":"  Run code in the chroot before customisation or packages are installed. A good"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_49e996a8","line":101,"in_reply_to":"5f7c97a3_7bc5493c","updated":"2018-07-09 17:57:04.000000000","message":"It is working but when you try to access the files placed using this variable on the install phase that var does not exist. Also there is no information on the phases that run inside chroot on how to access these files.\n\nWhat I saw for elements built in to diskimage-builder is that they map the `/tmp/in_target.d` on their install.d phase for example. That said I could not find the information being added here if I have not looked into the already created elements.\n\nThis variable actually maps the filesystem prefix used on the machine building the image. But anything placed inside it will have to access /tmp/in_target.d on phases that run inside the chroot. The first paragraph suggest to use this to copy files from the machine building the image to the chroot but never tells how to access it from within the chroot and that is the hole point of this addition.","commit_id":"33756305fcccca7cd4247dfbf246792d8c294314"}]}