On 17-Apr-99, 22:20 (CDT), "Brian E. Ermovick" <[EMAIL PROTECTED]> wrote:
>
> Manually getting rid of those *~'s isn't really an answer, either. I think
> a package should have the right to rm -r any directory that's not used by
> another package, empty or not.
(The following example from a dis
James Troup <[EMAIL PROTECTED]> writes:
> The phone calls do often cause delays.
Isn't there some information I can add to the developer's reference
about (a) what time of day they should expect your call (GMT) and,
maybe (b) giving new-maintianer the right phone number or a couple of
numbers in
On Sat, Apr 17, 1999 at 10:20:50PM -0500, Brian E. Ermovick wrote:
> vim has that annoying (although occasionally helpful) habit of making
> those *~ files whenever a file you've edited with it has been changed.
Occasionally? OCCASIONALLY?! :)
Anyhow, if you don't like that behaviour, turn it off
> > You've got to be careful how you phrase that -- it could cause some pretty
> > serious problems if / isn't explicitly owned by some package, for example.
> > Otherwise, I agree. Debian claims jurisdiction over everything except
> > /opt, /usr/local, and /home ...
> Hrmm -- hehe -- pretty goo
> Manually getting rid of those *~'s isn't really an answer, either. I think
> a package should have the right to rm -r any directory that's not used by
> another package, empty or not.
You've got to be careful how you phrase that -- it could cause some pretty
serious problems if / isn't explicit
> A package owns its custom directories (/etc/foo), and could delete it
> *if it is empty* (although I think dpkg ought to do this, but I'm not
> sure if does). If it's not empty, then it shouldn't delete it, because of:
>
> A package should never ever erase any other files.
Hrmm -- the only prob
6 matches
Mail list logo
