#44077: How can I activate old version of dependency in Portfile? --------------------------------+-------------------------------- Reporter: harshil.makwana@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.0 Resolution: | Keywords: Port: | --------------------------------+-------------------------------- Changes (by cal@…): * cc: harshil.makwana@… (removed) * type: defect => enhancement * component: ports => base Comment: Also, you don't need to Cc yourself, this is not a defect, and for the next time, the macports-users lists is the proper place for discussions like these. -- Ticket URL: <https://trac.macports.org/ticket/44077#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#44077: How can I activate old version of dependency in Portfile? --------------------------------+-------------------------------- Reporter: harshil.makwana@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.0 Resolution: worksforme | Keywords: Port: | --------------------------------+-------------------------------- Changes (by cal@…): * status: new => closed * resolution: => worksforme Comment: OK, so there's nothing more to be done here. I'm going to close this ticket as `worksforme`, because I don't know a use-case where this would be appropriate, and you aren't sharing your motivation for what you've done. I am aware of `registry_activate` and that it can be used in Portfiles, I however seriously doubt doing so is a good idea, and it will fail if the outdated version of port you're trying to activate isn't installed on a user's system. The correct way to solve an incompatibility with an upgraded dependency is 1. asking upstream to fix it 2. trying to patch for compatibility with the new version yourself 3. providing a separate port for the older version, ensure that it can be installed alongside the new port and modifying the dependency. If there is a port that no longer works with one of our upgraded dependencies you should file a bug against that port and we can figure out which of the mentioned steps we should take. Activating an older version is not a general solution to the problem. -- Ticket URL: <https://trac.macports.org/ticket/44077#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#44077: How can I activate old version of dependency in Portfile? --------------------------------+-------------------------------- Reporter: harshil.makwana@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.0 Resolution: worksforme | Keywords: Port: | --------------------------------+-------------------------------- Comment (by cal@…): That still doesn't explain why building your port against the current version of the dependency is not an option. -- Ticket URL: <https://trac.macports.org/ticket/44077#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#44077: How can I activate old version of dependency in Portfile? --------------------------------+-------------------------------- Reporter: harshil.makwana@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: base | Version: 2.3.0 Resolution: worksforme | Keywords: Port: | --------------------------------+-------------------------------- Old description:

Hi, We know that we can not specify version in dependency library but If it is possible to activate old version in portfile using TCL script then It is good for me.Please reply me If you know something about this. Thanks in advance.

New description: Hi, We know that we can not specify version in dependency library but If it is possible to activate old version in portfile using TCL script then It is good for me.Please reply me If you know something about this. Thanks in advance. -- Comment (by cal@…): OK, so you're trying to do something MacPorts wasn't built for. I'm not stopping you, I'm just telling you. Glad you were able to figure it out, but that's not something we're going to support in the near future. -- Ticket URL: <https://trac.macports.org/ticket/44077#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X