Opened 16 years ago
Last modified 9 years ago
#16574 new enhancement
Portfiles need to be able to declare a dependency on a base version
| Reported by: | macosforge.org@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | MacPorts Future |
| Component: | base | Version: | 1.6.0 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), kballard (Lily Ballard) | |
| Port: |
Description
from ticket:11935:1
"We do want Portfiles to be able to declare a dependency on a base version, but that's not possible at the moment."
Change History (5)
comment:1 Changed 16 years ago by jmroot (Joshua Root)
| Type: | defect → enhancement |
|---|
comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… eridius@… added |
|---|
comment:3 Changed 16 years ago by afb@…
There is PortSystem, for introducing breaking changes to the Portfile syntax...
comment:4 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
But we've broken the Portfile syntax in many releases by introducing new keywords which previous versions of MacPorts can't parse, yet we haven't ever increased the value of PortSystem beyond 1.0.
comment:5 Changed 9 years ago by neverpanic (Clemens Lang)
r134511 introduced macports_version, which allows ports to check for their base version. Not exactly the same, but a step in the right direction.
Note: See
TracTickets for help on using
tickets.
I think what we have right now is simpler -- assume all ports require the latest released version of MacPorts. I don't think anybody wants to go through our > 5000 ports to figure out which minimum version of MacPorts each requires.