Hi,
I agree. It would be cleaner. But I don't like it that the backward
compatibility is broken. Wcd has been backward compatible since the
start, that is over 12 years.
In enterprise network systems people use the -u option to jump to
directories of colleagues. If you move data files you break this
functionality, because there are still people using older versions of
wcd. I see it also at my work. People keep on using old versions for
long time. I want to bother them to upgrade. Such systems can have
hundreds of users, and you have no control, about which version of wcd
they use.
Also many users will have to move custom made tree files. There are even
people who build scripts around wcd. I want to keep them happy.
``Software is like sex. Make one mistake, and support it for the rest of
your life.'' ;-)
This was not a big mistake. It's only about a few files. I prefer
keeping people happy.
Erwin
Op 05-03-09 13:23, Jari Aalto schreef:
Erwin Waterlander <water...@xs4all.nl> writes:
The amount of data that is stored by for instance Mozilla under ~/.mozilla
is enormous ...
There are many application that only have few files. Exerpts:
[DIR] ~/.ccache/:
CACHEDIR.TAG
stats
[DIR] ~/.dillo/:
adblock.txt
cookiesrc
cookies.txt
dpi_socket_dir
[DIR] ~/.gstreamer-0.10/:
registry.i486.xml
registry.x86_64.bin
[DIR] ~/.putty/:
sshhostkeys
[DIR] ~/.VirtualBox/:
compreg.dat
VirtualBox.xml
xpti.dat
[DIR] ~/.xfe/:
trash
xferc
...
The point is not, how many. It's more clean to have each application to
reserve its own directory
~/.<application 1>/
~/.<application 2>/
~/.<application 3>/
In my $HOME directory I have 244 hidden files and directories.
ls -a | grep '^\.' | wc -l
244
Most wcd users will have only 2 .wcd files in $HOME...
From the original report:
Any help managing that is welcomed. There are benefits in separate
dirs:
- backup by directory
- version control by directory
- ignore directories from searches; find(1) etc.
Jari
