On Wed, 23 May 2012, Rodolfo kix Garcia wrote:
In this debian package version (0.95.3), I will continue using /etc/GNUstep/Defaults, to avoid delay in the package creation. But, I think that I should change the folder in future versions in upstream.

I for myself don't feel the necessity to change things like these paths (and CamelCase names for that matter) as I don't get what's wrong with them but here are some comments nevertheless.

The main problem is the uniformity between the files in /etc and the files in $HOME, because they should be the same structure. OTOH WindowMaker don't have relation with GNUstep now, therefore, we should change the GNUstep to "other thing", probably WindowMaker or wmaker. IMO, I prefer configuration files starting with dot in my home directory, therefore ".WindowMaker" or ".wmaker" could be a good idea, using then /etc/WindowMaker or /etc/wmaker.

I don't like the .WindowMaker because usually other such directories start with a lowercase letter and using a capital letter would make it non-uniform with them (besides Carlos' apparent dislike of the CamelCase :-)). You might consider .config/wmaker which seems to be the trend nowadays and I like it because it reduces the number of dot files in my home directory. But the best option may be to use a configure option (such as --with-configdir) to make it settable at compile time and then everyone could decide which path to use. You could preserve the default in upstream and set something else Debian likes in the deb package.

I think that we can make the change, because WindowMaker can search the configuration files using different folders (see defaults.c), and then, we can read the files at /home/user/.wmaker, if not exists, then at /home/user/GNUstep, else, the common files at /etc/wmaker, else /usr/.../WindowMaker/.

Yes, it's a good idea to preserve compatibility so that users don't have to change their existing config and it still works. Please make sure that old config is still found.

Regards,
BALATON Zoltan


--
To unsubscribe, send mail to [email protected].

Reply via email to