Fix the META.json license entry #461
Conversation
The link was broken and the license appears to be the MIT license, so switch to that.
|
Sorry to be so late in getting to this. As you might have noticed, pg_diffix is abandoned. We are instead pursuing SynDiffix, which is generally easier to use. May I ask what your interest in pg_diffix is? |
|
Just fixing it so it's listed on PGXN properly. |
|
Ok but (I admit out of curiosity) why do you bother fixing it if it is not
something you want to use?
…On Tue, Sep 17, 2024 at 4:36 PM David E. Wheeler ***@***.***> wrote:
Just fixing it so it's listed on PGXN <https://pgxn.org/dist/pg_diffix/>
properly.
—
Reply to this email directly, view it on GitHub
<#461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQP5KKI7T7EDG25GSSPPZ3ZXA45BAVCNFSM6AAAAABNE4WHC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGA2DOOJUGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I'm working on binary packaging for PGXN as well as a rewrite of its metadata standard that includes license specification based on the SPDX License List. I'll eventually be migrating everything on PGXN and ned to update the license (so will map pg_diffix to the proper license), and wanted to get you all updated before you made another release. I did not know it was discontinued. One goal for binary packaging is to build packages for everything on PGXN, which means repairing and patching a few things. Will perhaps have to create some sort of annotation for deprecated or archived extensions, I guess. Does SynDiffix run as a Postgres extension? |
|
Since pg_diffix is no longer supported, should we just remove the extension?
…On Thu, Sep 19, 2024 at 4:26 PM David E. Wheeler ***@***.***> wrote:
I'm working on binary packaging for PGXN as well as a rewrite of its
metadata standard that includes license specification based on the SPDX
License List <https://github.com/spdx/license-list-data/>. I'll
eventually be migrating everything on PGXN and ned to update the license
(so will map pg_diffix to the proper license), and wanted to get you all
updated before you made another release. I did not know it was discontinued.
One goal for binary packaging is to build packages for everything on PGXN,
which means repairing and patching a few things. Will perhaps have to
create some sort of annotation for deprecated or archived extensions, I
guess.
Does SynDiffix run as a Postgres extension?
—
Reply to this email directly, view it on GitHub
<#461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQP5KPQMETI6OZCYNXQHNDZXLNIFAVCNFSM6AAAAABNE4WHC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRRGE2DQMBUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
On Sep 21, 2024, at 11:00, Paul Francis ***@***.***> wrote:
Since pg_diffix is no longer supported, should we just remove the extension?
PGXN does not currently have a way to delete extensions.
|
The link was broken and the license appears to be the MIT license, so switch to that.
Looks like all existing releases on PGXN are using the Business Source License 1.1, so when it switches to using SPDX licenses it will reindex older versions with that license.