Trash specification, version 0.1

[David Faure]

On Thursday 02 September 2004 13:36, mr at ramendik.ru wrote:
> 
> >> I have somewhat lost track of th eother-partitions issue. Is the
> >> consensus
> >> on administrator-created $topdir/.Trash , and $uid directories within
> >> it?
> >
> > Yes, and if that doesn't exist, the app can try using/creating a global
> > $topdir/.Trash-$uid directory.
> 
> I'm not sure this is a good idea. A trash listing app would have to search
> every top dir for BOTH .Trash/$uid and .Trash-$uid.
> 
> I would say, there should be an admin-created $topdir/.Trash, and if it's
> not there, trashing is done by copying to $HOME. And implementations *may*
> include some form of auto-cteation of .Trash (would be a nice improvement
> for removable devices).

Let's see: if a user creates a .Trash (as one could do on a floppy disk, or on a
partition mounted for one user only), then other users will either:
- be able to use that directory (e.g. g+w is set by the umask); no problem
   (it would be wise to g-w the $uid subdirs themselves of course).
- not be able to use that directory (can't mkdir in it); well, they'll use their $HOME.

So I agree with $topdir/.Trash, either created by root or by user, 
and $uid/ subdirs inside it.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).