Skip to content

WIP: Request to remove ruby 1.8 from the tree#1322

Merged
domenkozar merged 1 commit intoNixOS:masterfrom
zimbatm:no-ruby18
Mar 7, 2014
Merged

WIP: Request to remove ruby 1.8 from the tree#1322
domenkozar merged 1 commit intoNixOS:masterfrom
zimbatm:no-ruby18

Conversation

@zimbatm
Copy link
Member

@zimbatm zimbatm commented Dec 3, 2013

To continue the discussion on #1272 , ruby 1.8 is unsupported by the ruby dev team and has known vulnerability issues. I propose to we remove it from the tree.

There's two blockers: klinkstatus and s3sync.

klinkstatus seem to compile fine without ruby18 but I'm not sure exactly how the kde {} derivation work.

s3sync seems to be an old ruby1.8 script that interacts with S3. It doesn't seem to be maintained anymore: http://s3sync.net/wiki ( the new maintainer has just pushed 1 commit and didn't release anything). Either find a replacement, upgrade the script or just remove it all-together.

TODO:

  • klinkstatus
  • Find a solution for s3sync
  • actually remove ruby18

@Phreedom
Copy link
Member

Phreedom commented Dec 4, 2013

I don't think removing ruby18 is a good idea, it sitll may be useful to
someone for legacy stuff, since ruby19 is not backwards-compatible. Fixing our
packages to not use it is something that definitely makes sense.

@zimbatm
Copy link
Member Author

zimbatm commented Dec 6, 2013

Maybe it would be worth applying that last round of patches then: https://blog.heroku.com/archives/2013/12/5/a_patch_in_time_securing_ruby

@ghost ghost assigned nbp Jan 12, 2014
@domenkozar
Copy link
Member

Looks good, feel free to open an issue to track progress for s3sync.

domenkozar added a commit that referenced this pull request Mar 7, 2014
WIP: Request to remove ruby 1.8 from the tree
@domenkozar domenkozar merged commit 3e2f390 into NixOS:master Mar 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants