On Oct 2, 2007, at 16:16, N_Ox wrote:
Le 2 oct. 07 à 13:05, Michael Wild a écrit :
Anders F Björklund wrote:
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.
I second that.
Or perhaps a bit a more elaborate scheme like fink uses it: namely
a stable and an unstable tree.
Would make things much more reliable.
I would rather see this problem resolved by working on a major
modification against base/ code:
multiple versions for each port.
Only one tree would be required, and we could use a fine-grained
dependency system as it is in Gentoo Portage.
For what purpose? We already have the situation that when we want to
make, say, both apache 2.0 and apache 2.2 available, we create two
ports: apache20 and apache2, respectively. This works fine. What do
you need in addition to that?
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
