Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removal of Code Supporting Legacy Distros (3.10 tasks) #82

Closed
dtrudg opened this issue Jun 3, 2021 · 1 comment · Fixed by #703
Closed

Removal of Code Supporting Legacy Distros (3.10 tasks) #82

dtrudg opened this issue Jun 3, 2021 · 1 comment · Fixed by #703
Labels
roadmap Features / changes that are scheduled to be implemented techdebt

Comments

@dtrudg
Copy link
Member

dtrudg commented Jun 3, 2021

Type of issue
technical debt

Description of issue
SingulartyCE contains various workarounds for RHEL6 / 2.6 kernel, old versions of invoked external programs etc. Special cases supporting these distributions can be removed gradually, but 4.0 is a good target to have removed all to simplify maintenance.

This relates to the host on which Singuarity is installed, not the age of the containerized OS.

  • Remove workaround for squashfs-tools < 4.3
  • Remove remaining EL6 test conditionals
  • No need to handle _LINUX_CAPABILITY_VERSION_2
@dtrudg dtrudg added the techdebt label Jun 3, 2021
@dtrudg dtrudg added this to the SingularityCE 4+ milestone Jun 3, 2021
@dtrudg dtrudg added the roadmap Features / changes that are scheduled to be implemented label Jul 2, 2021
@dtrudg
Copy link
Member Author

dtrudg commented Jan 24, 2022

We aren't jumping to a CE 4.0 soon, so this will be taken on as time permits in 3.x milestones.

@dtrudg dtrudg changed the title Removal of Code Supporting Legacy Distros Removal of Code Supporting Legacy Distros (3.10 tasks) Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Features / changes that are scheduled to be implemented techdebt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant