#29756 closed submission (fixed)
py27-antlr3: new port
| Reported by: | marc.schlaich@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | singingwolfboy@… | |
| Port: | py27-antlr3 |
Description
Attachments (1)
Change History (5)
Changed 13 years ago by marc.schlaich@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | singingwolfboy@… added |
|---|---|
| Owner: | changed from macports-tickets@… to ryandesign@… |
| Status: | new → assigned |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
| Summary: | python27 runtime for antlr3 → py27-antlr3: new port |
I updated py26-antlr3 to 3.1.3, fixed its livecheck, and indicated that it is noarch in r79303, and corrected its primary category in r79304. Then I copied that py26-antlr3 to py27-antlr3, changed the maintainer to you, and committed it in r79305.
It would be good if py26-antlr3 and py27-antlr3 could be updated to new versions simultaneously, so it would be nice if David could comaintain py27-antlr3 with you, since he already maintains py26-antlr3, or if py27-antlr3 could be marked as openmaintainer, as py26-antlr3 is, so that others could commit updates to it without having to wait for your approval.
comment:3 Changed 13 years ago by singingwolfboy@…
I'm also fine with giving maintainership of the py26-antlr3 port to Marc, if he wants it. I don't use antlr3 nowadays, and I don't have much reason to maintain it.
comment:4 Changed 13 years ago by marc.schlaich@…
I'm only working a few weeks on antlr3, so the openmaintainer marking would be the best solution I think.
Thanks.