Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 368451 - gnustep-base/gnustep-make-2.6.0 installs invalid /etc/GNUstep/GNUstep.conf so that openapp can't find gnustep applications
Summary: gnustep-base/gnustep-make-2.6.0 installs invalid /etc/GNUstep/GNUstep.conf so...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Gnustep project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 12:06 UTC by Sergey Ilinykh
Modified: 2011-06-08 09:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Ilinykh 2011-05-23 12:06:22 UTC
Because gnustep-base/gnustep-make-2.6.0 installs invalid /etc/GNUstep/GNUstep.conf
openapp can't find gnustep applications.

All paths in this config file must be fixed to proper defaults.

Reproducible: Always
Comment 1 Bernard Cafarelli gentoo-dev 2011-06-06 19:23:28 UTC
Hi, is this after an update? openapp works here on all my boxes with new gnustep-make and new layout

If yes, please check that the configuration file is up-to-date (etc-update, dispatch-conf, ...), and that all gnustep packages were re-emerged in the new layout (/usr/GNUstep should be empty).

If that is the case, can you attach GNUstep.conf to this bug, and post the exact openapp error message?
Comment 2 Sergey Ilinykh 2011-06-07 02:47:27 UTC
I tried to reemerge gnustep-make but reinstalled GNUstep.conf still had invalid paths.

I'll give you more info in hour
Comment 3 Sergey Ilinykh 2011-06-07 08:39:58 UTC
I just noticed. I used deprecated GNUSTEP_LOCAL_ROOT in my ebuild.
so my app was installed in wrong dir. I rewrote ebuild to use GNUSTEP_LOCAL_APPS and now openapp works fine with it.

Probably GNUSTEP_LOCAL_ROOT should be set with the same value as GNUSTEP_LOCAL_APPS until removed from config at all.
or just close this bug as invalid.

btw, why gnustep-base_src_unpack calls gnustep-base_src_prepare? its one of reasons why I don't use gnustep eclasses.
Comment 4 Bernard Cafarelli gentoo-dev 2011-06-08 09:12:39 UTC
Indeed these old variables still worked with the old layout, but they are broken for fhs and possibly other layouts, from gnustep-make release notes:
`GNUSTEP_xxx_ROOT'
     The variables GNUSTEP_SYSTEM_ROOT, GNUSTEP_LOCAL_ROOT,
     GNUSTEP_NETWORK_ROOT, GNUSTEP_USER_ROOT and GNUSTEP_ROOT are
     deprecated in gnustep-make version 2 and you should never use them.
     gnustep-make version 2 supports installation domains that are
     mapped to filesystem locations in arbitrary ways; for this reason,
     a variable like GNUSTEP_SYSTEM_ROOT has no longer any use.

     If your GNUmakefiles contains references to GNUSTEP_SYSTEM_ROOT (or
     similar), you should remove them by replacing them with references
     to the actual logical directory into which you want to install.
     For example, if your GNUmakefile is trying to install something
     into GNUSTEP_SYSTEM_ROOT/Library/Libraries, you need to replace it
     with GNUSTEP_SYSTEM_LIBRARIES.  Please check the file `filesystem'
     for more information on the available variables.

So the best way is as you did to use the current variables :)

As for gnustep-base_src_unpack, this one is only exported for EAPI 0 and 1, where src_prepare does not exist and all "prepare" tasks had to be done in src_unpack.

gnustep-base_src_prepare should be harmless by itself, does it break something for your makefile? Don't hesitate to mail me (or gnustep@gentoo.org) if you have questions on the eclasses