1 |
On 21-07-2009 13:33:26 +0200, Markus Duft wrote: |
2 |
> i spent another few hours on getting this right. attached is a (way |
3 |
> smaller) new version of the patch, making both interix and winnt work. |
4 |
> the patch is written as such, that other platforms may be easily added |
5 |
> in the future (i think of hppa-hpux and aix - i talked to haubi, and the |
6 |
> format of the NEEDED.PFX.1 files is ok - if not, we can still |
7 |
> change :)). |
8 |
|
9 |
I actually don't understand why you took .PFX this time. It seems this |
10 |
stands for Prefix, as the python code is doing now too. I don't really |
11 |
understand what Prefix is different from ELF in this case. It works |
12 |
fine on Linux and Solaris ELF in Prefix. So what was the idea behind |
13 |
PFX? I think ITX was better. If it's really because you hate to waste |
14 |
space in the python code on inventing new format names, you might better |
15 |
call it ELFLIKE or something. However, the MACHO case won't ever fit in |
16 |
it, and we decided to split it off, because that also will make other |
17 |
tools that read/use it fail because of file not found, instead of not |
18 |
understanding the file format, or its contents. |
19 |
|
20 |
So please consider this. What's the benefit of squeezing them all into |
21 |
one file/format? Only if you're absolutely sure this is completely |
22 |
compatible, and also for the future, without harming others, then it |
23 |
could be done. But on the other hand, giving each its own file name |
24 |
takes not much more, especially if they share the implementation, but |
25 |
allows easy upgrade/bump/migration if ever they /need/ to be |
26 |
fixed/changed/etc. |
27 |
|
28 |
|
29 |
|
30 |
-- |
31 |
Fabian Groffen |
32 |
Gentoo on a different level |