[MacPorts] #40794: grass @6.4.3: upgrade postgresql variants
#40794: grass @6.4.3: upgrade postgresql variants -----------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -----------------------------+-------------------------------- This is a request to upgrade the postgresql variants a bit and provide variants +postgresql92 and (maybe) +postgresql93, the first becoming the default. This is particularly interesting because other ports now default to +postgresql92. So the current situation is a bit messy and one would and up with two postgresql versions by default. +postgresql93 might become more relevant in future. To my understanding postgresql83 is not maintained any more. From the grass webpage I see no clear indications nor contraindications about which versions exactly are compatible. {{{ grass @6.4.3 (gis) Variants: ffmpeg, mysql5, postgresql83, postgresql84, postgresql90, postgresql91, sqlite3, universal, wxPython, wxwidgets }}} -- Ticket URL: <https://trac.macports.org/ticket/40794> MacPorts <http://www.macports.org/> Ports system for OS X
#40794: grass @6.4.3: upgrade postgresql variants ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: | ------------------------------+-------------------------------- Changes (by mojca@…): * status: new => closed * resolution: => fixed Comment: Sure, committed in r112311. However I didn't test anything as I'm not really able to make the port work reliably. I didn't make any postgresql variant the default one though, so the port still builds without PostgreSQL bindings. Please open a new ticket for that for either `egall` or any other future maintainer who cares about the port if you think that the bindings should simply always be enabled. Also, in case that you would like to volunteer for a port maintainer, we would be very happy and then you could do with the port "whatever your heart would please" ;). I already asked `egall` the same and I'm still waiting for him to collect the courage and to agree, but you could both be maintainers if both of you decide to work on the port. I don't know how to use the software, so I lack the proper motivation to look deep down and to try to fix the problems. -- Ticket URL: <https://trac.macports.org/ticket/40794#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#40794: grass @6.4.3: upgrade postgresql variants ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: grass | ------------------------------+-------------------------------- Changes (by macsforever2000@…): * port: => grass Comment: In the future, please fill in the Port field. -- Ticket URL: <https://trac.macports.org/ticket/40794#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#40794: grass @6.4.3: upgrade postgresql variants ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: grass | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): Replying to [comment:1 mojca@…]:
Sure, committed in r112311. However I didn't test anything as I'm not really able to make the port work reliably. Thanks!
I didn't make any postgresql variant the default one though, so the port still builds without PostgreSQL bindings. Please open a new ticket for that for either `egall` or any other future maintainer who cares about the port if you think that the bindings should simply always be enabled. Sorry, your right the port does not require any postgres variant, and it is okay like this. My confusion ;(
Also, in case that you would like to volunteer for a port maintainer, we would be very happy and then you could do with the port "whatever your heart would please" ;). I already asked `egall` the same and I'm still waiting for him to collect the courage and to agree, but you could both be maintainers if both of you decide to work on the port. Well, I am starting getting involved with MP and I might step in as maintainer on some ports. However, so far I know little about grass, so for the moment avoid becoming involved here, maybe at a later stage.
-- Ticket URL: <https://trac.macports.org/ticket/40794#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#40794: grass @6.4.3: upgrade postgresql variants ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: grass | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): Replying to [comment:2 macsforever2000@…]:
In the future, please fill in the Port field. Sorry for this, I should already know by now!
-- Ticket URL: <https://trac.macports.org/ticket/40794#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#40794: grass @6.4.3: upgrade postgresql variants ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: grass | ------------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:1 mojca@…]:
Sure, committed in r112311. However I didn't test anything as I'm not really able to make the port work reliably.
I didn't make any postgresql variant the default one though, so the port still builds without PostgreSQL bindings. Please open a new ticket for that for either `egall` or any other future maintainer who cares about the port if you think that the bindings should simply always be enabled.
Also, in case that you would like to volunteer for a port maintainer, we would be very happy and then you could do with the port "whatever your heart would please" ;). I already asked `egall` the same and I'm still waiting for him to collect the courage and to agree, but you could both be maintainers if both of you decide to work on the port.
I don't know how to use the software, so I lack the proper motivation to look deep down and to try to fix the problems.
I want to at least be able to get it fixed on my own computer before I agree to maintain it, and that requires fixing #40315 first. -- Ticket URL: <https://trac.macports.org/ticket/40794#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts