-
Notifications
You must be signed in to change notification settings - Fork 313
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
Include NOTICE.txt in release #622
Include NOTICE.txt in release #622
Conversation
With this commit we generate a NOTICE.txt file and include it in the Rally wheel as well as the offline distribution package.
|
||
echo "Preparing NOTICE file" | ||
__NOTICE_OUTPUT_FILE="${ABSOLUTE_DOWNLOAD_BIN_DIR}/NOTICE.txt" | ||
source "${SCRIPT_SRC_HOME}/../create-notice.sh" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Referencing a script from a different directory is not nice. I think we should move our build-related scripts to a dedicated directory. However, I wanted to keep the scope of this PR as small as possible.
} | ||
|
||
function main { | ||
cat NOTICE > "${OUTPUT_FILE}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how important it is, but does it make sense to use a variable name for NOTICE file? We are not likely to reuse it anywhere, so may be it's okay.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO it is ok to reference NOTICE
here directly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Thanks!
With this commit we generate a NOTICE.txt file and include it in the
Rally wheel as well as the offline distribution package.