#1040044 yajl: Move to better maintained fork

Package:
src:yajl
Source:
src:yajl
Submitter:
Bastien Roucariès
Date:
2023-07-02 04:33:03 UTC
Severity:
normal
#1040044#5
Date:
2023-07-01 16:33:09 UTC
From:
To:
Dear Maintainer,

yajl upstream seems to be dead

Could you please move to https://github.com/openEuler-BaseService/yajl

Thanks

rouca
#1040044#10
Date:
2023-07-02 04:21:23 UTC
From:
To:
Thanks.  I've been looking into this a bit today.

OpenEuler-BaseService did invite others to join their project:

https://github.com/lloyd/yajl/issues/243

However, I'm not seeing much activity there.  Their most recent commit
was over a year ago, and the differences between their fork and current
upstream amount to a few small patches.

The fork below seems more actively developed, and the committer seems
active in current upstream's issue reports, but a lot of work seems
focused on moving to BSDMake:

https://github.com/robohack/yajl


There are a lot of forks, each doing their own thing.  But unless one
really takes the lead, I'm not sure what benefit there would be in
switching upstreams.  Am I missing something?

John Stamp
#1040044#15
Date:
2023-07-02 04:21:23 UTC
From:
To:
Thanks.  I've been looking into this a bit today.

OpenEuler-BaseService did invite others to join their project:

https://github.com/lloyd/yajl/issues/243

However, I'm not seeing much activity there.  Their most recent commit
was over a year ago, and the differences between their fork and current
upstream amount to a few small patches.

The fork below seems more actively developed, and the committer seems
active in current upstream's issue reports, but a lot of work seems
focused on moving to BSDMake:

https://github.com/robohack/yajl


There are a lot of forks, each doing their own thing.  But unless one
really takes the lead, I'm not sure what benefit there would be in
switching upstreams.  Am I missing something?

John Stamp