Klaus Ethgen wrote:
> Am Mo den 17. Nov 2008 um  0:39 schrieb Omari Stephens:
>> (general response)
>> Admittedly, I'm loath to think that splitting things up by default is a good 
>> idea ??? the Windows Registry already went down this path, and it's an 
>> absolute 
>> nightmare to remove apps manually.  Of course, this XDG stuff does have a 
>> reasonable use-case in allowing apps to work in all sorts of "distributed" 
>> environments (with shared, read-only config partitions, or shared caches, or 
>> other stuff like that).
> 
> I share your opinion. But there is a gauge. I hate that every
> application is polluting my $HOME. The use of the XDG stuff would care
> about and put the stuff to common places. It was absolutely OK for
> applications to write to $HOME direct in past days where only few shared
> there life in the users $HOME but today that ended in a nightmare.
When is this a problem, and how would it become not-a-problem if all of those 
directories were to move to a common subdirectory?  My analysis of this reason 
has been the following:
1) Having tons of dot-dirs around might make directory reads take a long time
2) Having tons of dot-dirs around might make it hard to find a certain one that 
you're looking for
3) Having tons of dot-dirs around makes for a lot of clutter when you list the 
home directory

Clearly, using the XDG spec will have absolutely no effect on cases 1 and 2.  
As 
for case 3, I find myself asking "when do you list the home directory, 
including 
the dot-directories?"  Given that it's commonly-accepted that dotfiles are 
"hidden" to some extent, I wouldn't expect any graphical UI to display them 
without some option to filter them out.  And if you have them un-hidden because 
you need to put something inside of one, then you're back to case 2.

If there's something I'm missing or overlooking, please let me know.

> To have it sorted in special paths would help me to, for example, do a
> "rm -rf $HOME/.cache" to cleanup all the unneeded caching data. Moreover
> it can be easily linked to a memory file system like tmpfs.
This is a valid reason, and falls under "for the few who need it, it'll be 
tremendously useful" I think.

--xsdg


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geeqie-devel mailing list
Geeqie-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geeqie-devel

Reply via email to