JRuby

gem installation does not set executable rights correctly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: JRuby 1.0.1
  • Fix Version/s: JRuby 1.0.2, JRuby 1.1b1
  • Component/s: None
  • Labels:
    None
  • Environment:
    mac os x
  • Number of attachments :
    0

Description

on mac os x, when installing a gem, the default executable as identified in the gem is not correctly set with executable rights.

Activity

Hide
Charles Oliver Nutter added a comment -

And it works on trunk/1.1?

Show
Charles Oliver Nutter added a comment - And it works on trunk/1.1?
Hide
Charles Oliver Nutter added a comment -

1.0.x seems ok with Java 6; trying Java 5 next.

Show
Charles Oliver Nutter added a comment - 1.0.x seems ok with Java 6; trying Java 5 next.
Hide
Charles Oliver Nutter added a comment -

Ok, it's definitely not setting executable under Java 5. Java 5 provides no mechanisms for chmod and friends, so we have been spawning the external "chmod" command. My guess is that this is failing to launch correctly, but either way this is a very problematic area for us. The same problem would exist under JRuby trunk/1.1, but we have also introduced JNA to call the real POSIX chmod function when possible, so it will happen much less frequently. I will investigate whether chmod is not spawning correctly under Java 5. Other suggestion are welcome.

Show
Charles Oliver Nutter added a comment - Ok, it's definitely not setting executable under Java 5. Java 5 provides no mechanisms for chmod and friends, so we have been spawning the external "chmod" command. My guess is that this is failing to launch correctly, but either way this is a very problematic area for us. The same problem would exist under JRuby trunk/1.1, but we have also introduced JNA to call the real POSIX chmod function when possible, so it will happen much less frequently. I will investigate whether chmod is not spawning correctly under Java 5. Other suggestion are welcome.
Hide
Charles Oliver Nutter added a comment -

Ok, it looks like an issue where we need to pass the absolute path when launching chmod; modifying it to pass the absolute path appears to make chmod work correctly. I will commit this to trunk and 1.0 branch.

Show
Charles Oliver Nutter added a comment - Ok, it looks like an issue where we need to pass the absolute path when launching chmod; modifying it to pass the absolute path appears to make chmod work correctly. I will commit this to trunk and 1.0 branch.
Hide
Charles Oliver Nutter added a comment -

Fixed in 4317 on 1 .0 branch and 4318 on trunk.

Show
Charles Oliver Nutter added a comment - Fixed in 4317 on 1 .0 branch and 4318 on trunk.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: