MetPX / MetPX/sarrac

v2 (aka sarrac) is deprecated, should not be used in new installation.

Open
#156 1 comment 0 reactions 0 assignees View on GitHub
bug enhancement Policy wontfix
Dominant language
C
Stars
4
Forks
1
Avg merge
5d 1h
Merged PRs (30d)
1

Description

Please use metpx-sr3c package for any new deployments.
* This issue refers to all sarrac (on v2_* branches) (v2_dev, v2_stable, etc...)
* the major deployments of the C package are all on the version 3 branch.
* major changes in symbolic link handling, directory handling, and v03 message format are not present in the v2 tree. v2 only implements earlier iterations of the v03 format, and cannot accept or produce currently valid v03 messages.
* There may also be changes in paths generated so that even the v02 messages do not work well with an sr3 workflow.
* the C version 3 is aligned with the sr3 (python version 3) system.
* One cannot control/integration v2 C with sr3 python management ui.

Why is v2 still around:
* the python v2 library does integrate with the obsolete sarrac package.
* There are some deployments still using it.

All users recommended to upgrade to metpx-sr3c (version 3 package of C bindings.)

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the v2_* branches and any installation or deployment guidance referring to sarrac, then compare the recommendation with the metpx-sr3c package and the sr3 Python management UI. The issue names no files or tests. Done means clearly marking v2 as deprecated and directing new deployments to metpx-sr3c while explaining why existing deployments may remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.