Package marked as broken, install from Github source?

Zirias

Son of Beastie

Reaction score: 1,711
Messages: 2,871

freejetz888 anything you find in Mk/ inside the ports tree. Especially Mk/bsd.port.mk has extensive documentation in the comments on top of the file. But the first thing to consider is indeed the handbook. Only if you miss some info there, it helps to look directly into the ports' make framework :cool:
 

astyle

Daemon

Reaction score: 671
Messages: 1,507

Set DEFAULT_VERSIONS+= pgsql=10 in /etc/make.conf. Then everything you build from ports will be build against PostgreSQL 10. You can change the defaults when you build from ports. See /usr/ports/Mk/bsd.default-versions.mk.
I would disagree with that, I'd rather modify the port's makefile to tell it to require pgsql v.10... Messing with make.conf can have unintended consequences down the road, especially when a given version reaches EOL.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 12,767
Messages: 39,377

Messing with make.conf can have unintended consequences down the road, especially when a given version reaches EOL.
And a dozen or so custom edits to various ports won't? Really, I much rather have this done in one place that's specifically meant for this exact purpose. Sure you have to keep track of what versions are actually available but you have to do that anyway.
 

Zirias

Son of Beastie

Reaction score: 1,711
Messages: 2,871

Indeed, there's no question about it: DEFAULT_VERSIONS is the mechanism explicitly meant to be used for that. The consequence when using a version that's removed will be that your builds will fail (which I wouldn't call unintended...) and if you use DEFAULT_VERSIONS, there's only one single place where you have to edit something.

freejetz888 when you're finished with your installs (or upgrades?), could you give feedback whether the package is actually operational correctly? thanks ;)

edit: after fixing some "obvious" (side note, C++ stinks *fg*) runtime issues over in the PR (thanks for taking it there directly) and I'm still waiting for my fixes to be committed – I'd still be interested to learn whether the package now works as expected in actual use :cool: Maybe the new maintainer is reluctant to commit without knowing for sure everything is sorted out now 🤷‍♂️
 

Zirias

Son of Beastie

Reaction score: 1,711
Messages: 2,871

The fully fixed port finally made it into main. freejetz888 if you're still around, it would still be nice to know whether it actually works correctly – so far I only know it loads correctly…
 
Top