[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Structure in $HOME
From:       "Manuel Amador (Rudd-O)" <amadorm () usm ! edu ! ec>
Date:       2003-02-03 15:54:34
[Download RAW message or body]

>
>
>>>so, if it is left out of the GUI (we can discuss merits of that
>>>separetly, or not at all =), what are your thoughts on it being
>>>configurable instead of harcoded to $KDEHOME/share/cache?
>>>      
>>>
>>If you want to have it somewhere else you can symlink it to where you want
>>it.
>>    
>>
>
>this is a viable end-user solution? how can a sys admin make this a policy 
>that gets propagated to all (new) users by default?
>
>yes, there are work arounds, but they are just workarounds. i can see benefits 
>to having it configurable[1], but what are the downsides? more processing at 
>start up since it wouldn't be hardcoded anymore? or do you feel that this is 
>one of those sorts of features that sounds good to have but would never or 
>rarely ever get used in real life making it just more baggage?
>
>i'm just trying to understand =)
>
>[1]  being able to put caches in an area of the fs that gets purged regularly; 
>$KDEHOME may be on a network fs but you want the caches to be on local disk 
>for speed and bandwidth issues, easy relocation of the cache dir to cooperate 
>with other environments...
>
Well, you could make a script that goes into every user's home directory 
and kills the cache dir.  That isn't hard to do.  That way you can evict 
the caches whenever you feel like it's convenient.
But caches have to be in the home directory: they're private data.

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]