For MacPorts 1.6.0,

I think you should split the "dports" trunk in two,
"trunk" and "release", just as done with the "base".
There is just too much port breakage with running the
latest developer version on the user machines, IMHO.

It also needs a cooler name... Such as "Evolution",
as in: I'm running the latest MacPorts Evolution. :-)

--anders

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to