Task Summary
We have decided not to maintain system-requirements-lock.txt as a checked-in file. Keeping the lock file synchronized with requirements.txt introduces significant maintenance overhead, and the lock file itself is inherently environment specific. Dependency resolution can vary across operating systems, Python versions, hardware configurations, and over time as package repositories evolve, making a static shared lock file difficult to keep accurate.
Instead, we will move to a runtime-generated approach. The system dependencies will be resolved in the target environment when needed, likely by installing the system requirements into a temporary environment and generating the fully resolved dependency list using pip freeze. This ensures that conflict detection is performed against the actual installed dependency set for the current environment rather than against a potentially stale or inaccurate lock file.
Task Type
Task Summary
We have decided not to maintain system-requirements-lock.txt as a checked-in file. Keeping the lock file synchronized with requirements.txt introduces significant maintenance overhead, and the lock file itself is inherently environment specific. Dependency resolution can vary across operating systems, Python versions, hardware configurations, and over time as package repositories evolve, making a static shared lock file difficult to keep accurate.
Instead, we will move to a runtime-generated approach. The system dependencies will be resolved in the target environment when needed, likely by installing the system requirements into a temporary environment and generating the fully resolved dependency list using pip freeze. This ensures that conflict detection is performed against the actual installed dependency set for the current environment rather than against a potentially stale or inaccurate lock file.
Task Type