How image installs work [was Re: The image question]

[Daniel J. Luke]

On Mar 9, 2007, at 12:32 PM, Vincent Lefevre wrote:
> On 2007-03-09 09:53:56 -0500, Daniel J. Luke wrote:
>> Here's another variant of that:
>
>> 1 - libfoo.dylib v. 1.0 comes out and it is so good that everyone  
>> starts
>> writing apps that use it.
>> 2 - a serious security flaw is found in libfoo and is fixed in  
>> libfoo v. 1.1
>> with no api/abi changes
>> 3 - oh no, since we're "solving the fragile dependency problem" we  
>> now need
>> to re-build/re-link every application that depended on libfoo  
>> since we
>> installed it into a version-dependent directory
>
> This shouldn't be a version-dependent directory, but an API-dependent
> directory, so that it wouldn't be needed to rebuild everything if the
> API doesn't change.

That's not how image mode works now - and I'm not sure that we want  
to impose the burden of verifying abi/api compatibility between  
releases on every portfile author (if we were to add hooks to make  
things work that way).

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20070309/3bebdb93/PGP.bin