Ticket #32933 (closed enhancement: fixed)
py-blist: Integrate py31-blist, add py32-blist
| Reported by: | mistersheik@… | Owned by: | stromnov@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | phw@…, mistersheik@… | |
| Port: | py-blist py31-blist py32-blist |
Description
Copy: /trunk/dports/python/py31-blist/Portfile
To: /trunk/dports/python/py32-blist/Portfile
Changing PortGroup to "python32 1.0", and name to "py32-blist"
Thanks!
Change History
comment:1 Changed 16 months ago by ryandesign@…
- Cc phw@… added
- Owner changed from macports-tickets@… to stromnov@…
- Summary changed from Copy py31-blist to py32-blist to py-blist: Integrate py31-blist, add py31-bilst
- Type changed from request to enhancement
- Milestone MacPorts Future deleted
comment:6 Changed 16 months ago by mistersheik@…
Would it be possible possible to have a temporary py32-blist before the more elegant solution is implemented? Right now, not having blist in Python 3.2 is the only thing preventing my upgrade.
comment:7 Changed 13 months ago by jmr@…
- Port changed from py32-blist to py-blist py31-blist py32-blist
- Summary changed from py-blist: Integrate py31-blist, add py31-bilst to py-blist: Integrate py31-blist, add py32-bilst
comment:8 Changed 13 months ago by jmr@…
- Summary changed from py-blist: Integrate py31-blist, add py32-bilst to py-blist: Integrate py31-blist, add py32-blist
comment:9 Changed 13 months ago by stromnov@…
- Status changed from new to closed
- Resolution set to fixed
Thanks!
py32-blist variant added in r92563.
comment:10 Changed 13 months ago by jmr@…
That commit only fixed half of this; py31-blist is still in a separate portfile.
BTW you don't need to increase the revision when adding a new subport.
Note: See
TracTickets for help on using
tickets.
We would rather incorporate py31-blist into the existing unified py-blist port, and then add a py31 version.