Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jan 2019 19:46:29 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 235330] install: relative symlink bug
Message-ID:  <bug-235330-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235330

            Bug ID: 235330
           Summary: install: relative symlink bug
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: mat@FreeBSD.org
             Flags: mfc-stable11?, mfc-stable12?

$ mkdir /tmp/lib/ /tmp/libexec
$ touch /tmp/lib/foo.so
$ install -lrs /tmp/lib/foo.so /tmp/libexec/
$ ls -l /tmp/libexec
total 1
lrwxr-xr-x  1 mat  wheel  9 30 janv. 20:34 foo.so -> ../foo.so


This only happens with absolute paths, and only, from what I undestand with=
 a
bit of testing, if the first path matches the second.  As in "/tmp/lib" is
present in "/tmp/libexec", so, hey, they must be the same, so stop here, but
"/tmp/libexec" is not in "/tmp/lib" so add a "../"

install -lrs is used quite a lot in the ports tree, and this bug broke at l=
east
a port.

Also, an EN would be nice once this is fixed and merged to the different st=
able
branches.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235330-227>