Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-13 Thread Helge Hess 

On 10. Mrz 2006, at 20:13 Uhr, Jeremy Bettis wrote:

You can't have every platform tested for every release.


But you need to decide (and declare!) what platforms are actually  
tested prior a release. Otherwise a stable release is pretty useless,  
no?


For GNUstep this means that there needs to be a decision whether it  
supports Windows in releases or not. Which in turn has direct  
consequences on whether this can be a marketing feature or not.  
(don't tell someone that gstep-base works on Windows if a downloaded  
*release* doesn't ...)


Even for GCC, windows is on the non-critical list.  I am a heavy  
Mingw user (the only heavy mingw user of gnustep?)  and I don't  
care if Mingw is tested before every release.  Frankly the idea of  
someone who never normally uses windows dual booting over to  
windows once every 3 months to test under mingw before calling the  
version RELEASE, doesn't really boost my confidence any.


Well, the usual way it works is that you have multiple people  
responsible for reporting on whether a certain state of the source  
(usually the RC, release candidate) works on 'their' platform.
Of course for mingw32 this should not be someone who doesn't use  
Windows ...


More exactly basically every major project doing stable releases  
has AT LEAST a beta cycle, usually there is also an RC cycle. GNUstep  
has nothing like that and the 'releases' are nothing more than tagged  
alpha releases.

Not a good base to build upon :-(

BTW: even if you don't want to fix a certain platform support for a  
given release, its much better to know whether a releases does  
support that platform in advance. So that the release announcement  
can be correct ...


Greets,
  Helge
--
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-10 Thread Jeremy Bettis 

Alex Perez wrote:
Shouldn't we make it a formal policy to test under mingw before making 
any RELEASE? Is there a checklist everyone much follow before making a 
release? It should probably be on the wiki, perhaps locked/in 
review-submit-only mode so it can only be edited by the respective 
package maintainers.


What do you think of this suggestion?
You can't have every platform tested for every release.  Even for GCC, 
windows is on the non-critical list.  I am a heavy Mingw user (the only 
heavy mingw user of gnustep?)  and I don't care if Mingw is tested 
before every release.  Frankly the idea of someone who never normally 
uses windows dual booting over to windows once every 3 months to test 
under mingw before calling the version RELEASE, doesn't really boost my 
confidence any.





___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-07 Thread Richard Frith-Macdonald 


On 6 Mar 2006, at 15:39, Tom Koelman wrote:



Hi,

I am fixing the Windows Installer with regard to the GNUstep.conf
file. I am building base 1.11.2 and gui 0.10.2.


base 1.11.2 was unfortunately not tested on mingw, and released broken.
I would therefore rather take a recent snapshot from svn and use that.
I believe the current state is good ... certainly I used it a few  
days ago.


./configure --disable-xml --with-config-file=$GNUSTEP_INSTALL_DIR/ 
GNUstep.conf


Disabling xml is no longer necessary if you use the modified libxml  
as described in the README.MinGW in the current make package.


2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE  
value ('/etc/GNUstep/GNUstep.conf') is not an absolute path.   
Please rebuild GNUstep-base specifying a valid path to the config  
file.


What do I do wrong? As far as I can tell I already build GNUstep-base
specifying a valid path to the config file.


base now uses native windows paths ... current make/base configure  
scripts set up two separate config files, one for the unix-style make  
environment, and one for  the windows-style runtime environment.



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-07 Thread Tom Koelman 
Sheldon Gill [EMAIL PROTECTED] writes:

 I use the following incantations:
 In the directory with source of GNUstep make:
 cd /gnustep-source/make
 ./configure --prefix=$GNUSTEP_INSTALL_DIR 
 --with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
 make install
 [...] Build ffcall [...]
 # Build and install the base library itself
 cd /gnustep-source/base
 ./configure --disable-xml 
 --with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
 make install messages=yes warn=no
 Now, if I run the defaults.exe program or some other GNUstep using
 program I get the following:
 2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE value
 ('/etc/GNUstep/GNUstep.conf') is not an absolute path.  Please
 rebuild GNUstep-base specifying a valid path to the config file.
 What do I do wrong? As far as I can tell I already build
 GNUstep-base
 specifying a valid path to the config file.

 If you have specified a file and it's been picked up correctly you will find 
 your definition in:
   core/base/Source/config.h

 I suggest you check that first.

My config.h does not contain a definition of GNUSTEP_CONFIG_FILE. It
does contain this:

/* Disable GNUSTEP_CONFIG_FILE environment variable */
#define OPTION_NO_ENVIRONMENT 1

 Are you using the *release* of base 1.11.2 or a later CVS version?

Yes, I am using the release.

Is there maybe some documentation about the way this configuration
file configuration works?

Regards,
Tom Koelman


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-07 Thread Richard Frith-Macdonald 


On 7 Mar 2006, at 06:47, Tom Koelman wrote:


Is there maybe some documentation about the way this configuration
file configuration works?


Yes ... 'configure --help' for the make and base packages, though  
this changed quite a bit between the last release and the current  
code in svn.


For information on what can go in the config file, you can refer to  
the base reference documentation (Documentation/Base/Base.html) ...  
of course, first you have to configure and build base and generate  
the documentation :-(
The *intent* is that the default config should work without any  
hassle, so that you only need to read the documentation to tweak  
things later.  So we do need to put an effort into making the initial  
install smooth and reliable.



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-07 Thread Sheldon Gill 

Tom Koelman wrote:

Hi,

I am fixing the Windows Installer with regard to the GNUstep.conf
file. I am building base 1.11.2 and gui 0.10.2.

I use the following incantations:

In the directory with source of GNUstep make:

cd /gnustep-source/make
./configure --prefix=$GNUSTEP_INSTALL_DIR 
--with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install

[...] Build ffcall [...]

# Build and install the base library itself
cd /gnustep-source/base
./configure --disable-xml --with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install messages=yes warn=no

Now, if I run the defaults.exe program or some other GNUstep using
program I get the following:

2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE value 
('/etc/GNUstep/GNUstep.conf') is not an absolute path.  Please rebuild 
GNUstep-base specifying a valid path to the config file.


What do I do wrong? As far as I can tell I already build GNUstep-base
specifying a valid path to the config file.


If you have specified a file and it's been picked up correctly you will find 
your definition in:

  core/base/Source/config.h

I suggest you check that first.

Are you using the *release* of base 1.11.2 or a later CVS version?


Regards,
Sheldon






___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

2006-03-06 Thread Tom Koelman 

Hi,

I am fixing the Windows Installer with regard to the GNUstep.conf
file. I am building base 1.11.2 and gui 0.10.2.

I use the following incantations:

In the directory with source of GNUstep make:

cd /gnustep-source/make
./configure --prefix=$GNUSTEP_INSTALL_DIR 
--with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install

[...] Build ffcall [...]

# Build and install the base library itself
cd /gnustep-source/base
./configure --disable-xml --with-config-file=$GNUSTEP_INSTALL_DIR/GNUstep.conf
make install messages=yes warn=no

Now, if I run the defaults.exe program or some other GNUstep using
program I get the following:

2006-03-06 14:57:21.708 defaults.exe[3680] GNUSTEP_CONFIG_FILE value 
('/etc/GNUstep/GNUstep.conf') is not an absolute path.  Please rebuild 
GNUstep-base specifying a valid path to the config file.


What do I do wrong? As far as I can tell I already build GNUstep-base
specifying a valid path to the config file.

Regards,
Tom Koelman



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev