misc/compat5x package installs with weird messages

[Stephen Montgomery-Smith]

Pav Lucistnik wrote:
> Garrett Cooper píše v pá 14. 12. 2007 v 15:39 -0800:
>> Jan Henrik Sylvester wrote:
>>> Installing the 7.0-RELEASE package of graphics/xnview, I got some 
>>> weird messages that seem to come from the misc/compat5x dependency:
>>>
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat/libc.so.5: Operation not permitted
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat/libc_r.so.5: Operation not 
>>> permitted
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat/libcrypt.so.2: Operation not 
>>> permitted
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat/libpthread.so.1: Operation not 
>>> permitted
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat/libthr.so.1: Operation not 
>>> permitted
>>> rm: /var/tmp/instmp.qdjoSl/lib/compat: Directory not empty
>>> rm: /var/tmp/instmp.qdjoSl/lib: Directory not empty
>>> rm: /var/tmp/instmp.qdjoSl: Directory not empty
>>> pkg_add: couldn't remove temporary dir '/var/tmp/instmp.qdjoSl'
>>>
>>> What has happened?
> 
>> Files are still in use. Are you exec'ing a program that needs lib/compat5x?
> 
> There is nothing like "executable in use is undeletable" phenomenon
> that's observed on Microsoft Windows.
> 
> My bets are on noschg flag.

Pav, you are exactly right.  I have experienced this many times myself. 
  After installing the compat5x package you need to do "chflags -R 
noschg /var/tmp/inst* && rm -rf /var/tmp/inst*" or something like that.

I think it is a bug in pkg_install, that it doesn't check for the schg 
flag being set in its temporary file area.  Or maybe it should set the 
flags in the first place.

Stephen