gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: ~/GNUstep/Defaults/.GNUstepDefaults


From: Manuel Guesdon
Subject: Re[2]: ~/GNUstep/Defaults/.GNUstepDefaults
Date: Wed, 27 Nov 2002 21:44:47 +0100 (CET)

On Wed, 27 Nov 2002 14:19:30 +0000 Richard Frith-Macdonald <address@hidden> 
wrote:

 >| 
 >| On Wednesday, November 27, 2002, at 12:08  pm, Manuel Guesdon wrote:
 >| 
 >| > I've found a problem using an application compiled with a previous 
 >| > version of core/base (around
 >| > jully 2002).
 >| > A new  application has modified ~/GNUstep/Defaults/.GNUstepDefaults 
 >| > and make the
 >| > dictionary unreadable by the old application (sorry, I haven't kept 
 >| > the modified file but it
 >| > was a number coded as 7200 in previous version now coded  <*I7200> or 
 >| > something like that).
 >| >
 >| > It take me some time to guess why the application failed to run.
 >| > So is it possible to add versioning system in this kind of file so an 
 >| > new application won't badly
 >| > modify this file when the file version is older ?
 >| > Or use different file names for incompatible version
 >| > (~/GNUstep/Defaults/.GNUstepDefaults.x.y) or something else.... ?
 >| 
 >| Unfortunately the plist format (the old one, not the xml one) contains 
 >| no provision for versioning ...
 >| perhaps we should move to the new xml format for defaults?

It can be done by just adding an entry "Version" in the plist. If there's none, 
we can assume it's an old version.


 >| > Now, I have to make ~/GNUstep/Defaults/.GNUstepDefaults owned by root, 
 >| > writable only by the owner
 >| > and  readable by everyone (pplication fail to if it can't read the 
 >| > file) so old and new application can run..
 >| 
 >| Unless you use statically linked applications, your old apps can just 
 >| use the new library and work with
 >| the new format, so I didn't think this was likely to be a big issue.

It depends
I've freezed an application with it's own /usr/GNUstep tree so it won't 
conflict with new 
versions (which has method changes, libraries changes and so on). A "solution" 
is to run it under a different user but it's not a solution if someone want 
(for exemple) to use GNustep applications (mail,...)l for it's daily tasks and, 
on the same 
computer and identity) work with up-to-date cvs versions to develop/improve 
GNUstep or GNustep applications :-(

Manuel

--
______________________________________________________________________
Manuel Guesdon - OXYMIUM <address@hidden>
14 rue Jean-Baptiste Clement  -  93200 Saint-Denis  -  France
Tel: +33 1 4940 0999  -  Fax: +33 1 4940 0998





reply via email to

[Prev in Thread] Current Thread [Next in Thread]