Re: [Bug-stow] address@hidden: Bug#133243: stow deletes directories it did not create if they're empty.]

[Guillaume Morin]

Dans un message du 12 fév à  1:41, Gaël Roualland écrivait :
> > If you create a /usr/local/stow/foo/bin/bar file, then 'stow' the 'foo'
> > package, things works fine.
> > 
> > However, when I want to delete the 'foo' package, stow deletes the
> > /usr/local/bin directory, if it's empty. I think this is a bug, as stow
> > didn't create this dir in the first place.
> 
> Is that really a bug ?? if the directory was share/package, it would
> seem logical that stow removes it with the package. 
> 
> And except from hard coding some well know directories (bin, lib, etc,
> ...) in sto,w I don't see how to avoid these problems. And removing an
> empty directory is not a big deal since it contains nothing...

There is two possible behaviors

1) We remove empty directories. This is what we do at the moment.

2) If a directory is a symlink to the package directory, we remove it.
If it is not, we just leave it. Of course, this means that there will be
some leftovers. So we should print an warning, something like 'Warning:
foo is empty, Stow will not remove it. You might want to delete it
yourself'. We can image to introduce a switch to force the removing of
empty directories...

What I meant is to at least think about 2)...

What do you think ?

-- 
Guillaume Morin <address@hidden>

     Tu veux que les gens réagissent ? Alors commence par réagir (Lofofora)