biology/canu: Upgrade to 1.7 release
Approved by jrm (mentor) or wen (mentor)
Differential to be added to commit message
Details
Details
- Reviewers
jrm wen - Commits
- rP468321: biology/canu: Upgrade to 1.7 release
portlint -AC: looks fine
Passed poudriere on {10.4,11.1}-{amd64,i386}
Tested in production
Diff Detail
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 16307 Build 16248: arc lint + arc unit
Event Timeline
| biology/canu/Makefile | ||
|---|---|---|
| 53 | $$(...) ? It's not an issue here, but there are some compelling arguments. https://mywiki.wooledge.org/BashFAQ/082 | |
Comment Actions
Thanks, I'm actually agnostic about things like this (and disagree with any argument that one way should *always* be preferred). I just use whichever syntax is more readable in a given situation. In this case, I think `` is cleaner, because it stands out against the other $ chars in the string. Where there are quotes, I tend to prefer $(). As for nesting output capture, I just avoid it. I'll break it into two commands, the first being a variable assignment. As I've aged, I've shifted toward a preference for readability over hyper-efficiency and cleverness. ( More referring to C syntax regarding efficiency, it's a non-issue in shell commands). ;-)