On Wed, Mar 02, 2016 at 11:33:26AM +0100, Ricardo Wurmus wrote:
> For convenience we might also want to have per-profile settings that
> allow us to specify default overrides, so that no matter what ruby gem
> you add to the profile it will always use a fixed variant of Ruby to
> build it.
>
> The
Pjotr Prins writes:
> OK, back on the topic of conflicts between interpreters and modules:
>
> I realise the current system is fine as is!
>
> Sometimes it is good to go for a cycle run in the cold ;)
>
> GNU Guix does the right thing. It builds isolated packages, including
> interpreters and mo
OK, back on the topic of conflicts between interpreters and modules:
I realise the current system is fine as is!
Sometimes it is good to go for a cycle run in the cold ;)
GNU Guix does the right thing. It builds isolated packages, including
interpreters and modules. Next it puts them in a profil
On Sun, Feb 21, 2016 at 06:31:27PM +0100, Pjotr Prins wrote:
> Another option would be have a symlinked profile for every ruby interpreter
> with
> the full hash
>
> /var/guix/profile/per-ruby/ziy7a6zib846426kprc7fgimggh8bz97-ruby-2.1.3/
>
> which contains symlinks to the libraries/gems installe
Another option would be have a symlinked profile for every ruby interpreter with
the full hash
/var/guix/profile/per-ruby/ziy7a6zib846426kprc7fgimggh8bz97-ruby-2.1.3/
which contains symlinks to the libraries/gems installed against that ruby.
NOW we only need to tell the interpreter where to find
I am thinking about this again. It is relevant for all interpreters.
The real pain is that between Ruby interpreters the profile can be shared which
contains a path to the modules, e.g. say ruby-nokogiri. Currently you can run
guix package -i ruby ruby-nokogiri
ruby -e "require-2.2.1 'nokogir
