Re: GNU Guix 0.2 released

[Ludovic Courtès]

Germán Arias <address@hidden> skribis:

> On 2013-05-17 07:27:10 -0600 address@hidden (Ludovic Courtès wrote:
> [snip]
>> 
>>> The only difference is that if the system don't know about the gnustep
>>> tools. The
>>> user will need run the gnustep script, something like ".
>>> /usr/.../GNUstep.sh", to set
>>> up the variables of gnustep environment.
>> 
>> What do you mean with “doesn’t know about the GNUstep tools”?  When is
>> it necessary to source that script?  What are the variables to be
>> defined?
>
> GNUstep can be installed using differents layouts. By default gnustep is
> installed using the FHS layout. But one popular layout is "gnustep", this
> install all in "/usr/GNUstep". Since this isn't an standard path to install
> libraries, headers and tools, the user need add this path or run the
> gnustep script at session startup or run it when he will use the
> gnustep-make tool.

OK.  As you may have seen, Guix installs each package in a directory of
its own (like GNU Stow, if that’s more familiar).  This is why Guix
already has the necessary infrastructure to set search path environment
variables like CPATH and LIBRARY_PATH (GCC’s search paths for headers
and libraries).

I guess GNUstep packages wouldn’t mind being installed each in their own
directory, provided the relevant search path environment variables are
set, right?

>> Guix has a mechanism to automatically define search path variables:
>> 
>>   http://lists.gnu.org/archive/html/bug-guix/2013-03/msg00158.html
>> 
>> Would that be of any help?
>
> I think it can help. Although I'm not an expert in what does exactly
> the gnustep script. I send you it attached if you want take a look.
> Anyway, installing gnustep with FHS layout, avoids the use of
> this script.

Well, it’s a lengthy script, but it seems that one of the important
variables is GNUSTEP_SYSTEM_ROOT, and perhaps
GNUSTEP_{LIBRARIES_,TOOLS_,}PATHLIST.

I guess we’ll need your GNUstep expertise to sort this out.  :-)

Ludo’.