[Slackbuilds-users] Changes Postgresql SBo scripts as version numbering has changed?

[Adis Nezirovic]

Sebastian, you are right, we've switched to 10.2 not too long ago, and
I've forgot to shorten PG_VERSION to 10 only. I'll update the script,
but we have to be careful, since there might be people who have
datadir at /var/lib/pgsql/10.2/data.

Best regards,
Adis

On Sun, Mar 18, 2018 at 1:04 PM, Sebastian Arcus <s.arcus at open-t.co.uk> wrote:
>
> On 18/03/18 11:47, Sebastian Arcus wrote:
>>
>> As Postgresql number scheme has changed with version 10 (and going
>> forward), and only the first number is the major version number, I was
>> wondering if it is worth amending the SBo scripts to reflect that. The data
>> dir, bin dir and log dir usually need to only be prefixed with the major
>> number, not the full version - to help with upgrades from one major version
>> to another.
>>
>> I would have made a patch myself, but I got a bit lost on how the old SBo
>> scripts used to use the full (e.g. 9.6.2) version in postgresql.SlackBuild,
>> yet end up with only the major version (e.g. 9.6) further down the line, in
>> rc.postgresql, setup.postgresql and other scripts - so maybe someone can
>> help?
>
>
> Partially answering the question myself - in postgresql.SlackBuild there is
> a "VERSION=" and a "PG_VERSION=". It looks like "PG_VERSION=" would need to
> be amended to 10, instead of 10.2 - and hopefully everything else would fall
> into place.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>