xCode 4.1 ?

[Tabitha McNerney]

Thank you Ryan for your feedback on this issue. Its too bad that Apple
always has to change something with each major OS upgrade to the point that
it breaks so many things. Sigh. But that's the world we live in and for many
people its advantageous to have OS X and its vagaries.

Jeremy, thank you also for listing the ports that have worked for you on
Lion so far. I am definitely going to try using precompiled binaries and
libraries on Lion to see what happens (it may be a week or two before I can
get to that but will send a message to the mailing list here to help out
other members of the MacPorts community).

-Tabitha

On Thu, Jul 21, 2011 at 4:29 PM, Ryan Schmidt <ryandesign at macports.org>wrote:

>
> On Jul 21, 2011, at 15:37, Tabitha McNerney wrote:
>
> > Hello, I saw the mention that there might be some 'port pkg' issues with
> Lion. Generally, is there any idea how many ports this affects? It might be
> nice to have some statistics such as "x% of ports are affected by this Lion
> issue" or something like that?
>
> I would expect 100% of ports are affected by this issue when using the
> command "port pkg" and 0% of ports are affected by this issue when using
> other port commands that have nothing to do with packaging like "port
> install".
>
>
> > Otherwise, how's it going with installing ports on Lion?
>
> Probably there are hundreds of broken ports at this time, since Lion just
> came out yesterday. It will probably be months before most of them are fixed
> (and years until they all are, based on experience with past OS upgrades).
> If you want a stable system, don't upgrade to Lion at this time.
>
>
> > What about ports that were already made from sources and installed on
> Snow Leopard, can they run ok as binaries on such a system upgraded to Lion?
>
> Maybe? No idea. Try it out.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20110721/b9e50dda/attachment.html>