You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
× failed to parse pixi.toml from /path/to/prj
╰─▶ failed to parse project manifest
Since the pixi is installed by each developer of a prj, and the pixi is now released about weekly, multiple versions of pixi would be a problem to reproducibility. Some new features could help this kind of project with many developers:
min-version under project table or pixi under system-requirements table indicates the pixi version requirement. (also require the backward compatibility). when an old pixi builds a project, it can auto self-update to the minimal required version.
all in project source, an wrapper entrypoint injected into project (like gradle/maven wraper), find or install on the fly the required version.
The text was updated successfully, but these errors were encountered:
Ah sorry, you mean an old version of pixi cannot parse a new version's pixi.toml. Yeah that is indeed tricky. We should start with versioning the toml indeed.
How about, in case or parsing error, checking manifest against most recent schema (hosted somewhere), and offering self-update if it passes? For instance with this https://github.com/tamasfe/taplo ?
OK, this should work. Whereas some cons to consider: a) this means backward compatibility after stable releases, and cannot introduce breaking change on the schema of pixi.toml; b) self-update may conflicts with the pkg manager (e.g. brew); c) A more complicated case, if two projects are build at the same time, the self-update may also fail.
Problem description
Since the pixi is installed by each developer of a prj, and the pixi is now released about weekly, multiple versions of pixi would be a problem to reproducibility. Some new features could help this kind of project with many developers:
min-version
underproject
table orpixi
undersystem-requirements
table indicates the pixi version requirement. (also require the backward compatibility). when an old pixi builds a project, it can auto self-update to the minimal required version.The text was updated successfully, but these errors were encountered: