On Fri, 6 May 2005, Jeremy C. Reed wrote:

> But the pkg_delete only showed the "Delete directory" for the @dirrm
> listed in x11/kdelibs3/PLIST. And it never showed the +DEINSTALL message
> about applications.menu (the CONF_FILES).

I now see this is correct behaviour. Although I'd like to add a message if
it verbose is set so pkg_delete will tell that it is running the
DEINSTALL_FNAME.

> I don't think it is a kdelibs3 problem. But maybe a problem with
> pkg_delete.

I added -x to top of each + script and pkg_delete again.

It is running the +DEINSTALL and its related scripts.

> This is FreeBSD 5.3-RELEASE. pkg_delete is from bootstrapping on March 8.

rmdir -p doesn't work like we expect:

> ls -la /usr/pkg/share/kde/applnk/Utilities/
total 4
drwxr-xr-x   2 root  wheel  512 May  6 07:32 .
drwxr-xr-x  12 root  wheel  512 May  6 08:07 ..

> sudo /bin/rmdir -p /usr/pkg/share/kde/applnk/Utilities
rmdir: /usr/pkg/share/kde/applnk: Directory not empty

> ls -la /usr/pkg/share/kde/applnk/Utilities/
total 4
drwxr-xr-x   2 root  wheel  512 May  6 07:32 .
drwxr-xr-x  12 root  wheel  512 May  6 08:07 ..

> sudo /bin/rmdir /usr/pkg/share/kde/applnk/Utilities

> ls -la /usr/pkg/share/kde/applnk/Utilities/
ls: /usr/pkg/share/kde/applnk/Utilities/: No such file or directory


What is up with the -p?

The behaviour is definitely different than normal (such as on NetBSD rmdir
will still complain that "Directory not empty" but it will still remove
the top level directories that are empty).

I think I had this same problem with the bulk builds not cleaning up too.

Now I see the problem with FreeBSD /bin/rmdir in their CVS. I will get a
newer /bin/rmdir :)

 Jeremy C. Reed

 	  	 	 open source, Unix, *BSD, Linux training
	  	 	 http://www.pugetsoundtechnology.com/