RFC: Introduce a new build section on spec to use with `package_dir` if required
@mudler is already working on this.
Since Mar 2, 2021.
- Dominant language
- Go
- Stars
- 307
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Inside the portage-tree with package per single package, there are a lot of layers and space required.
The use of the package_dir requires post-build steps that aren't really used in the next layers.
In general, in use cases like this, it's not needed that the files copied inside the package_dir directory that in a long time it duplicates the space required for the final image will be used.
Describe the solution you'd like
We could provide an epilogue section with steps that are executed in the images to get the package files but that isn't inside the pushed image.
epilogue:
- cp ${my_files} /${package_dir}/
It will add complexity but it reduces i/o operations that are very slow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.