I myself should be getting (again, more) re-engaged in the build/update process for PostgreSQL…
I’ll wake up shortly. Lou > On Apr 18, 2021, at 6:07 AM, Andreas Wacknitz <a.wackn...@gmx.de> wrote: > > Am 18.04.21 um 02:37 schrieb Austin Kim: >> On Apr 17, 2021, at 7:22 PM, Till Wegmueller <toaster...@gmail.com> wrote: >>> Hi Gary >>> >>> I use Postgres and extensions for all Applications I develop professionally >>> and privately. >>> >>> We use mostly 12 and upwards 13 being the standard and I am waiting for 14 >>> to hit. The last Bugfix release for 9.5 was on 2021-02-11 so quite recently. >>> >>> I would love to have 13 and modern 12 packaged, especially as we have a >>> build server for them sponsored by the Oi community. So we know it builds >>> even on current develop. >>> >>> My preference for the record is to have 13, 12 and 11. Older ones should >>> only be used for people still needing them. AWS only offers those in their >>> offerings as well, so not many people will want 10 or older. >>> >>> -Till >>> >>> On 17.04.21 18:46, Gary Mills wrote: >>>> OI currently has postgresql versions: 95 96 10 11 12 . The OI >>>> default, in shared-macros.mk, is 95 . However, the postgresql >>>> developers report that 95 is unsupported, but 13 is available and >>>> supported. Something has to change in OI to move forward with >>>> postgresql. >>>> Here are some actions that could be taken with OI. We could change >>>> the default version to 10. I, myself, would prefer 11. We could >>>> obsolete 95. I'd prefer obsoleting 95 and 96. We could add version >>>> 13, but only after 96 is obsoleted. We should limit the number of >>>> postgresql versions in OI, after all. Finally, we could make no >>>> obsoletions or additions, retaining even the unsupported 95. Which >>>> would you prefer? >>>> I have not investigated two questions. Perhaps you can tell me? What >>>> are the consequences of obsoleting 95? What are the consequences of >>>> the default change? >> Hi, >> >> Sorry for posting to this list as I’m only an OpenIndiana user, not a >> developer, but PostgreSQL is the DB I use most. > This is perfectly fine. > I just want to chime in here and say: You don't need to be a developer > in order to get involved in OpenIndiana! > Of course it is helpful to know some programming languages and build > systems. But many for aspects you don't need to be a professional > programmer. > > At the moment we lack volunteers in almost all areas, even those not > related to updating packages. Eg. we need people to enhance or update > our documentation, > we need testers and of course people who care for some packages. > > Nobody started as an expert in any of these areas. I am willing to help > people to get involved, eg. we can have video conferences where I can > demonstrate and teach how to update packages. > > Of course you need to devote some resources (time, build or test > environment, ...). I can assure you that you will learn a lot about > OpenIndiana, Solaris and other operating systems. > And you will see some insanity related to software development, > especially open source software development where projects make heavy > changes (like change the build system) in minor or even micro releases. > > Andreas > > _______________________________________________ > openindiana-discuss mailing list > openindiana-disc...@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
