Python 2.7 – allow another db version beside 4.8

Jan Stary hans at stare.cz
Mon Dec 25 19:30:03 UTC 2017


On Dec 25 10:04:33, vince at macports.org wrote:
> > On 24 Dec 2017, at 11:23, Jan Stary <hans at stare.cz> wrote:
> >> On Dec 24 05:19:35, jmr at macports.org wrote:
> >>> On 2017-12-24 04:28 , Clemens Lang wrote:
> >>> Is there a reason to not just always use a newer version?
> >> And to turn the question around, what is gained by using the newer version?
> > 
> > Exactly.
> > 
> > Insisting on the newest version of everything
> > has cost me countless hours of comutation spent on nothing
> > except "having the newest version" (with the newest bugs).
> 
> Well my initial request was not about using the last version, but being able to choose one version and stick to it through multiple ports that depend thereon. I have a 128 GB SSD, and I’d rather not squander space with installing different versions of the same software for no reason except that the Portfile doesn’t offer the possibility to pick the version I want.

Generally, I tend to let the port/package use any version,
unless there is a specific reason for some specific version.
For example, if a port requires Python, then I consider
_any_ installed python to satsfy this requirement,
unless there is a reason it has to be python36 (or whatever).

What is the right way to state this in a Portfile?

	Jan



More information about the macports-dev mailing list