On Mon, July 6, 2015 4:31 pm, Daniel Johnson wrote:
>
>> On Jul 6, 2015, at 1:46 PM, Hanspeter Niederstrasser
>> wrote:
>>
>> If a library changes its install_name from /absolute/path/to/foo.X.dylib
>> to @rpath/foo.X.dylib (X is the same, c_v is bumped), does this need a
>> new
>> libN package n
> On Jul 6, 2015, at 1:46 PM, Hanspeter Niederstrasser
> wrote:
>
> If a library changes its install_name from /absolute/path/to/foo.X.dylib
> to @rpath/foo.X.dylib (X is the same, c_v is bumped), does this need a new
> libN package name? The file is installed to the same location, so packages
If a library changes its install_name from /absolute/path/to/foo.X.dylib
to @rpath/foo.X.dylib (X is the same, c_v is bumped), does this need a new
libN package name? The file is installed to the same location, so packages
linking to the old absolute path dylib should still be able to find the
new
