#54045 closed update (fixed)
Update ripgrep to 0.5.1 version
| Reported by: | SuperBo (SuperBo) | Owned by: | seanfarley (Sean Farley) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | ripgrep |
Description
Ripgrep current latest version is 0.5.1 which was released on 04-09-2017. While the current port version is 0.2.3 which was released in Oct last year. This means that it is 7 month from the last update of ripgrep port.
Please update it to the latest version or pass it to another maintainer.
Change History (4)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
| Owner: | set to raimue |
|---|---|
| Status: | new → assigned |
| Version: | 2.4.1 |
comment:2 Changed 7 years ago by seanfarley (Sean Farley)
| Owner: | changed from raimue to seanfarley |
|---|---|
| Status: | assigned → accepted |
I can do this now, actually (randomly have the time this morning).
comment:3 Changed 7 years ago by seanfarley (Sean Farley)
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
comment:4 Changed 7 years ago by raimue (Rainer Müller)
Thank you for providing the update. The port is openmaintainer, so others are welcome to contribute updates. That includes external contributors, just attach a patch for review to a ticket or open a pull request.
One of the problems with packaging ripgrep is that we do not have any infrastructure for Rust packages yet. At the moment the build phase will fetch and install whatever version is available at the time of building. My plan was to implement proper cargo dependencies, but did not get around to it yet due to other stuff.
In the future, please Cc the port maintainers (
port info --maintainers ripgrep), if any.