From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: guix environment Date: Mon, 15 Jun 2015 09:14:21 +0200 Message-ID: <87oakhigtu.fsf@elephly.net> References: <20150615065554.GA17263@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4ObM-0003ro-FZ for guix-devel@gnu.org; Mon, 15 Jun 2015 03:14:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4ObL-00058n-Im for guix-devel@gnu.org; Mon, 15 Jun 2015 03:14:36 -0400 In-reply-to: <20150615065554.GA17263@thebird.nl> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Pjotr Prins Cc: guix-devel@gnu.org Pjotr Prins writes: > Is there a way guix could quickly print out the information it now gives after > a successful package install: > > The following environment variable definitions may be needed: > export PATH="/home/pjotrp/.guix-profile/bin:/home/pjotrp/.guix-profile/sbin" > export PKG_CONFIG_PATH="/home/pjotrp/.guix-profile/lib/pkgconfig" > export GUILE_LOAD_PATH="/home/pjotrp/.guix-profile/share/guile/site/2.0" > export GUILE_LOAD_COMPILED_PATH="/home/pjotrp/.guix-profile/share/guile/site/2.0" > export CPATH="/home/pjotrp/.guix-profile/include" > export LIBRARY_PATH="/home/pjotrp/.guix-profile/lib" > export ACLOCAL_PATH="/home/pjotrp/.guix-profile/share/aclocal" > export LOCPATH="/home/pjotrp/.guix-profile/lib/locale" "guix package --search-paths" should do that. The only obstacle I see in evaluating this automatically in profiles is that same variables are not merged automatically, e.g. PYTHONPATH for different versions of Python. > Would it be OK to add some RUBY paths? This is done on the package level. LV2 audio plugins, for example, suggest the LV2_PATH variable to be set. For Ruby this could be done by the build system. ~~ Ricardo