ncurses layout violation

[goalieca@…]

ncursesw @5.8_0 - Received the following warning when building (dependency of fsharp)

--->  Fetching ncursesw
--->  Verifying checksum(s) for ncursesw
--->  Extracting ncursesw
--->  Configuring ncursesw
--->  Building ncursesw
--->  Staging ncursesw into destroot
--->  Installing ncursesw @5.8_0
--->  Activating ncursesw @5.8_0
--->  Cleaning ncursesw
--->  Fetching ncurses
--->  Verifying checksum(s) for ncurses
--->  Extracting ncurses
--->  Applying patches to ncurses
--->  Configuring ncurses
--->  Building ncurses
--->  Staging ncurses into destroot
Warning: violation by /usr
Warning: ncurses violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases!
--->  Installing ncurses @5.8_1+universal
--->  Activating ncurses @5.8_1+universal
--->  Cleaning ncurses

[blb@…]

Can you show the output from running the following?

$ port contents ncurses|grep usr

FWIW my ncurses didn't put anything in /usr, though I did not build it +universal...

[goalieca@…]

Here's what I found. It was on a completely fresh install too.

unicron:~ ryan$ port contents ncurses|grep usr
  /usr/lib/pkgconfig/form.pc
  /usr/lib/pkgconfig/menu.pc
  /usr/lib/pkgconfig/ncurses++.pc
  /usr/lib/pkgconfig/ncurses.pc
  /usr/lib/pkgconfig/panel.pc

[jmr@…]

Can't reproduce with or without universal.

[blb@…]

Is there a /usr/bin/pkg-config (which there shouldn't be, I believe)? Any changes to binpath in macports.conf? You can see with

grep binpath /opt/local/etc/macports/macports.conf

[goalieca@…]

It does appear there is. I certainly never modified it by hand though.

# paths are given in the example; it need not be uncommented.  Customizing binpath is intended for advanced users only.
#binpath		/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin
# while processing ports. As with binpath, setting extra_env is intended for

[blb@…]

It's there, but commented-out, so that's the default value; I was mostly curious if it wasn't commented-out and had something other than the default...

What about the pkg-config in /usr/bin, is there one there? If not, I'm all out of ideas.

[stefano+macports@…]

Replying to blb@…:

It's there, but commented-out, so that's the default value; I was mostly curious if it wasn't commented-out and had something other than the default...

What about the pkg-config in /usr/bin, is there one there? If not, I'm all out of ideas.

Well, I got the same problem with the usr violation. I have a pkg-config (symilnk) in /usr/bin placed by the mono framework.

[jmr@…]

Wow, that's about literally the worst place they could have chosen to install their stuff. If we don't support having anything in /usr/local we certainly don't support having random non-Apple-supplied files in /usr. See if r76982 helps anyway.

[goalieca@…]

Replying to jmr@…:

Wow, that's about literally the worst place they could have chosen to install their stuff. If we don't support having anything in /usr/local we certainly don't support having random non-Apple-supplied files in /usr. See if r76982 helps anyway.

I've applied that patch and all looks good though I wasn't able to do a complete reinstall from scratch and test (need my repo in working state today)