We've been discussing on IRC whether we want a new tree for 10.10's packages and no upgrade from 10.9, or to allow an in-place upgrade from 10.9 and keep their packaging in a common tree.
One idea that came up was to have a 10.9 tree and to move 10.9-specific package descriptions to that. The reason we didn't create a 10.9 tree at the time it was released was that we were still supporting 10.6, and there was a lack of enthusiasm for having to deal with three trees. On the other hand, there is a fairly large divergence between 10.9 and 10.8/7, and early signs indicate that the divergence between 10.9 and 10.10 won't be large (at least initially) so having a common tree and an upgrade option makes some sense to me. We'd do this by having a CVS freeze, apart from generating the 10.9 tree, and then releasing a new fink for 10.9 which uses the real 10.9 directory instead of putting in a 10.9->10.7 symlink. We'd probably update for 10.7 and 10.8, too, to add 10.9 to the SelfupdateCVSTrees list. Once that's out we'd unfreeze CVS, and folks would need to remember to update for 10.9 and 10.8/10.7 separately. We could actually do this at any point rather than waiting for Yosemite's release. Any thoughts on this idea? -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ 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
