Pros:

1) We're back to one architecture (albeit with two C++ ABI standards).
2) We're back to one package tree.
3) Fewer platforms to have to test base packages on.
4) No feelings of guilt for people who have been only updating for 10.7+ 
(OK, there probably aren't many of those).
5) Minimal effort to do it.  We just ensure that the next fink release 
won't bootstrap on 10.6 and don't put a .info file there, rather than 
doing a 10.6-EOL directory (though that will also work).
6) "Sorry, we don't support that OS any more"  has a nice ring to it.

Cons:

1) People will complain.  Though it's not like we said "10.6 is 
unsupported, so make sure to 'rm -rf /sw'.

It'd be nice to get this done in a couple of weeks.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to