You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Lacton (JIRA)" <ji...@apache.org> on 2008/08/04 13:50:46 UTC
[jira] Closed: (BUILDR-112) Using a user gem repository with 'rake
setup'
[ https://issues.apache.org/jira/browse/BUILDR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lacton closed BUILDR-112.
-------------------------
> Using a user gem repository with 'rake setup'
> ---------------------------------------------
>
> Key: BUILDR-112
> URL: https://issues.apache.org/jira/browse/BUILDR-112
> Project: Buildr
> Issue Type: Improvement
> Components: Core features
> Environment: Trunk revision 680587.
> Ubuntu
> Reporter: Lacton
> Priority: Minor
> Fix For: 1.3.3
>
> Attachments: BUILDR-112.patch
>
>
> On a linux system, a user can create his own gem repository by setting the GEM_HOME environment variable (e.g./home/lacton/local/opt/gemrepository). This way, this user does not need root access to install and update gems.
> 'rake setup' assumes that users on linux will be sudoers and that they will use the root gem repository, even though the user may have set his GEM_HOME.
> I propose that 'rake setup' does not call 'sudo' if GEM_HOME is set.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.