[Bug 30647] New: $WINEPREFIX "not owned by you" unnecessarily restrictive

http://bugs.winehq.org/show_bug.cgi?id=30647

Bug #: 30647
           Summary: $WINEPREFIX "not owned by you" unnecessarily
                    restrictive
           Product: Wine
           Version: unspecified
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

I am unable to point my WINEPREFIX at a path that is off an ext2 partition, or
more specifically, a vboxsf mount.

$ mkdir /vboxsf/HostUser/workarea-linux/wine-1
$ WINEPREFIX=/vboxsf/HostUser/workarea-linux/wine-1/; export WINEPREFIX
$ wine winecfg
wine: /vboxsf/HostUser/workarea-linux/wine-1 is not owned by you
$ ls -ld /vboxsf/HostUser/workarea-linux/wine-1
drwxrwxr-x 1 root sharedfs 0 May 11 22:16
/vboxsf/HostUser/workarea-linux/wine-1
$ id -a
uid=20000(shaddy) gid=20000(shaddy)
groups=20000(shaddy),27(sudo),10000(sharedfs)

It is true in this case, that I don't own the targetted directory. But you can
see that by group permissions, I have full access to that directory. In fact, I
created it. It is just not owned by me.

I've read up on this, and I've come to understand that the reason for this
setting is because people were "hosing" their ~/.wine when running as
root/sudo.

But the solution seems to me like applying "extreme prejudice". Wouldn't it
have been more polite to simply test for superuser-like privileges and then
disallow.

Even having a "relax, I know what I'm doing" override would make more sense to
me.

Any chance of making an improvement in this area?