-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There should be a single file zip rule #352
Comments
Since this is about "final layout of files", perhaps this functionality should be a per-file option in "pkg_install" ? |
I think that's an additional place where it has to work. If we are installing direct from the workspace maybe it's a single rule.
but maybe pkg_install works just like pkg_rpm and points to a set of srcs that know where they go in the system tree.
|
Hm. The idea of integrating it with We actually have a similar problem with regards to template expansion. Providing a single I haven't thought about this too much, but any of the options specified would be nice to have, or use as building blocks.
Perhaps, but fine-grained file controls better belong in |
This seems like overbuilding without a real need. Downgrading priority, but we should probably close it as pointless. |
Closing issues that no one is likely to work on for any forseable future |
To build some items like a Unix manual page, we want to simply gzip a file. That is, the source is "myprog.1" and the rule should generate "myprog.1.gz". Some ideas:
There are obvious tradeoffs w.r.t. actions to compress first and sending compressed files to the final package maker vs. just sending the files to the package maker and having it do it.
The text was updated successfully, but these errors were encountered: