Split build task in Rakefile
This might become a big more cleaner and Makefile like.
Also, since we cannot mount 9p filesystems with write easily (permissions-wise vs. the host, at least) our vagrant-libvirt setup has to write the artifacs to disk (inside the guest) as an intermediate step. If the build task is split up, the fetch can more easily be mixed in between the build and build dir teardown.
Related to Tails -
#5 Updated by intrigeri 2019-08-30 20:30:48
- Status changed from In Progress to Confirmed
- Assignee deleted (
- Priority changed from Normal to Low
> I might work on this sometime in the future if I there’s some additional reason for it — my current WIP indicates that it’s quite a bit of work, and the current motivation simply isn’t good enough.
I don’t think we’ve found some additional reason for it so far.
#6 Updated by intrigeri 2020-01-01 13:44:41
> Also, since we cannot mount 9p filesystems with write easily (permissions-wise vs. the host, at least) our vagrant-libvirt setup has to write the artifacs to disk (inside the guest) as an intermediate step.
Right. As demonstrated when using the attached commit, currently the main problem to avoid this intermediary step is that our
build-tails script will delete the build directory on exit, so if it does not move the build artifacts somewhere else first, there’s nothing left for
Rakefile to retrieve. To fix this, we would need to move the build dir cleanup work out of the
build-tails script (ideally to the Rakefile IMO, so that we can use Ruby instead of shell, and updates to this code don’t invalidate existing Vagrant build boxes), so that
rake build could run
build-tails, then retrieve artifacts, and finally ensure the cleanup code is run. Whether the build task is split along the way seems to be an implementation detail to me: per se, it’s not necessary to do that in order to drop the aforementioned intermediate step and get the corresponding build performance benefits.