[
https://issues.apache.org/jira/browse/HADOOP-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108253#comment-15108253
]
Chris Douglas commented on HADOOP-12651:
----------------------------------------
Since this is targeting trunk, it probably isn't necessary to redirect the old
scripts to invoke the new ones, even to remain compatible with existing
tooling/automation. A README under dev-support would be helpful, though. To
upgrade to new versions of Yetus, one bumps the version in yetus-wrapper?
Random:
* Downloading {{YETUS_KEYS}} and the {{.asc}} could probably be put within the
check for {{$GPGBIN}}. The keys file may change between versions, but wouldn't
be refetched, which could cause validation to fail (for obvious and easy to fix
reasons, but still).
* If the tarball exists but the result of extracting it doesn't, should this
attempt to re-download the tarball (and .asc), assuming the last one was
corrupt? The -f check that avoids the download seems more likely to wedge in
this case than avoid skippable work.
* Is the "z" option nonstandard for {{tar}}?
> Replace dev-support with wrappers to Yetus
> ------------------------------------------
>
> Key: HADOOP-12651
> URL: https://issues.apache.org/jira/browse/HADOOP-12651
> Project: Hadoop Common
> Issue Type: New Feature
> Components: scripts
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-12651.00.patch, HADOOP-12651.01.patch,
> HADOOP-12651.02.patch
>
>
> Now that Yetus has had a release, we should rip out the components that make
> it up from dev-support and replace them with wrappers. The wrappers should:
> * default to a sane version
> * allow for version overrides via an env var
> * download into patchprocess
> * execute with the given parameters
> Marking this as an incompatible change, since we should also remove the
> filename extensions and move these into a bin directory for better
> maintenance towards the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)