Erwin Waterlander <water...@xs4all.nl> writes:

>  Hi,
>
> I'm still not in favour of implementing this. I want wcd to stay
> backwards compatible. Old and new versions must be able to be used
> together in a multi user environment.
>
> I agree that the choice I made in the past (1996) was not ideal. It
> would be nicer to have all files under ~/.wcd, or named the files
> .wcd.* instead of .*.wcd. But I have had never any other report from
> people who had a problem with it. And there is always the option to
> use $WCDHOME. It's only about a few files. I think I make more people
> happy by keeping it the way it is.

1)

In some specific environment where $HOME are readable inside a company,
it may be desireable to be able to access other user's configurations.

It's just that in today's environment, the user accounts are pretty much
locked in elsewhere, so accessing other user's config for typical
university or polytechnic, or other non-corporate environments in
useually discouraged by policy.

So, I don't know is large user base would be affected if the default
were chnaged to use ~/.wcd and if not found, then revert back to the
old.

2)

The $HOME has been littering over the years as more and more software
put stuff under $HOME. This makes managing home a challenge.

The root of $HOME is worst place to put things. Although conveient for
few configurations, it starts to be annoying for 100-200 configurations
files.

The probelem:

    You can't version control each package's configs separately very
    easily if it puts directly to $HOME.

    But if package writes to $HOME/.<package>/  that directory can be
    esily
    - Backed up
    - put under version control
    - scp'd somewhere else to make a copy

    It also makes overall management simples when there would be always
    a <directory> (C.f how ~/.ssh/ manages files.

SUMMARY

So, if you could ponder this and perhaps consider how the change would
help the future needs.

Thanks,
Jari



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to