Replacing a file by a directory or vice versa

The way the update works, if a new version of a package got a directory in some place where a file was previously, it would fail because it wouldn't remove the file first. The other direction would pose the same kind of a problem.

Reassigned to @kkoci

@mvaner Do we want to force replace over existing? This can be most probably caused by user creating some folders or files where he shouldn't. But it would be rude from us to just remove it. What if we encounter something like this we would move it by appending for example -opkg-collision. With exception that when directory is empty (it self and its subdirectories contains no files) we would just remove it. Exception is because I think that there could be empty directories after some removed package.

I was mostly worried about an old and new version of a package (either the same or different one). I think that the only reasonable thing to do if we get a collision with what user put in there (eg. if it was a directory and we want to put a file there) is to error/die.

Updater doesn't leave empty directories behind, but I think it is still reasonable to get rid of empty directory if we need to put a file there.

Ok in such case, I will check how it would react, when update is replacing file with directory or otherwise, and possibly fix it. With exception of empty directory if it is not that case we would die (which is not what is happening now, currently even line about it is not printed as I tested it).

mentioned in merge request !113 (merged)

Status changed to closed

added Bug label and removed 1 deleted label