[MacPorts] #50427: sqlite3 @3.10.2_0 Cannot open database via symlink

[MacPorts]

#50427: sqlite3 @3.10.2_0 Cannot open database via symlink
-----------------------+--------------------------------
  Reporter:  hanche@…  |      Owner:  macports-tickets@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.3.4
Resolution:            |   Keywords:
      Port:  sqlite3   |
-----------------------+--------------------------------

Comment (by hanche@…):

 I'll get on their mailing list and report the bug that way.

 I looked at the upstream repository, and see that the bug is introduced
 with this checkin:

 {{{
 uuid:         c7c8105099c0412ac6c605f98987092c10bde57c 2015-10-31 17:58:33
 UTC
 parent:       9f19420b0a79dff65fc3a9d548f4b3fc4955f9f9 2015-10-30 20:54:25
 UTC
 merged-into:  6d5ce3ede4c7038c19a77268a5a7b9d5650933c2 2015-11-02 15:08:56
 UTC
 tags:         follow-symlinks
 comment:      On unix, if a file is opened via a symlink, create, read and
               write journal and wal files based on the name of the actual
 db
               file, not the symlink. (user: dan)
 }}}

 The trouble is in the function `unixFullPathname` in `src/os_unix.c`. It
 seems clear that it did not occur to the write of that patch that someone
 might refer to a symlink outside of the current directory. Ho hum.

 (I only mention this here for the record. I'll repeat it in my upstream
 bug report, of course. And I'll report back here.)

-- 
Ticket URL: <https://trac.macports.org/ticket/50427#comment:5>
MacPorts <https://www.macports.org/>
Ports system for OS X