smoothing leopard

[Daniel J. Luke]

On Oct 1, 2007, at 12:22 PM, Paul Phillips wrote:
> Leopard is supposed to come out this month (for real this time) and
> there are many ports that don't build - a lot more than there are bug
> reports.  Maybe it's not a big priority but if it's of interest I  
> have a
> leopard test system and can gather data on what doesn't build and why.
> If there is a consensus to let leopard settle further before worrying
> about it, then I don't want to clutter trac with bug reports.

I don't have Leopard seed access, so I haven't read the NDA, but it's  
possible that you are prohibited from doing that.

You may want to read the NDA over to make sure you can actually do it.

> Is there a clear delineation between what should be considered an
> upstream bug and what should be addressed in macports? Sometimes it's
> obvious but not always.

When it's not clear, I think we favor a two pronged approach (first,  
make things 'just work' by addressing it in macports. second, follow  
up with upstream and remove the macports patches when it gets fixed  
upstream).

--
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-dev/attachments/20071001/1deab1c5/PGP.bin