-
Notifications
You must be signed in to change notification settings - Fork 180
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial support for pkg_* rules as srcs of pkg_tar (#367)
* Initial support for pkg_* rules as srcs of pkg_tar 1. Create helper methods to turn srcs of type Pkg*Info into a manifest file that can drive pkg_tar. 2. Test generation of the manifest using those rules 3. Use it in pkg_tar 4. Change compute_data_path to use ctx as an input instead of output_file. This is important refactoring for a future step where we can move the loop which creates the manifest from srcs to a helper method that all the pkg_* rules can share. I can break that out to a cleanup first. 5. Add support for tree artifacts in the manifest and pkg_tar. Design points: - Do we disallow srcs with pkg_files to be mixed with remap in pkg_tar? - Does the pf test strategy, by looking at the generated manifest seem right? Next steps: - Now that we don't pass --files or --empty_dirs to build_tar, eliminate them from build_tar. Not done in this PR to keep it smaller. - we may need to add the concept of uid/gid to Package*Info along with username/group name. This is for tar, which can keep both. We do not have to solve this before moving on.
- Loading branch information
Showing
11 changed files
with
720 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.