Opened 15 years ago
Closed 15 years ago
#23714 closed update (fixed)
redland-bindings: update to 1.0.10.1
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | arto.bendiken@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | redland-bindings |
Description
redland-bindings should be updated to 1.0.10.1. The livecheck should be fixed too.
Attachments (1)
Change History (3)
Changed 15 years ago by CaptSolo
| Attachment: | Portfile-redland-bindings.diff added |
|---|
comment:1 follow-up: 2 Changed 15 years ago by CaptSolo
comment:2 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Replying to captsolo@…:
Attached a Portfile patch to update redland-bindings to 1.0.10.1. Also added a variant for python26.
Thanks, I committed this in r63907 with these changes:
- I dropped the revision down to 0
- I marked the python variants as conflicting with one another
I don't know about the "livecheck should be fixed" part, hence that is not fixed by this patch.
The livecheck feature is explained in the guide; it helps maintainers like you know when their ports might need to be updated. But for redland-bindings, it says:
$ port livecheck redland-bindings Error: cannot check if redland-bindings was updated (regex didn't match)
I fixed the livecheck in r63908 by copying the definitions from the redland port. Now you can use "port livecheck redland-bindings" to see if redland-bindings might need an update; no output means it probably doesn't.
The idea is you could use "port livecheck maintainer:arto.bendiken" to see if any of your ports might need updates. But you may need to fix livecheck definitions in your other ports too for that to work.
Attached a Portfile patch to update redland-bindings to 1.0.10.1. Also added a variant for python26.
I don't know about the "livecheck should be fixed" part, hence that is not fixed by this patch.