Dear fink-devel,
I've begun to implement the gcc 3.3 update, as I described in a few messages
in mid-August.
If you are interested in testing or assisting, here's what you need to do.
First, you can bootstrap fink running 10.2 and gcc3.3 if you check out the
CVS branch tagged "test_10_3" and bootstrap under 10.2. (The only difference
between that branch and HEAD, as of yesterday, was that both the 10.3-enabling
code and the 10.2-gcc3.3 enabling code only exist in that branch... also,
the 10.2-gcc3.3 subdirectory of the fink directory only exists there at
the moment).
Once you've bootstrapped, you'll find that fink is set up to use the new
10.2-gcc3.3 distribution rather than the usual 10.2 one, but that there
is almost nothing in that distribution yet!
Here's how I am constructing the 10.2-gcc3.3 distribution. I've made yet
a different CVS branch tagged "not_ready", and I dumped all the packages
from 10.2 into that branch. Before being moved from "not_ready" to HEAD,
for each package we need to
1) be sure that all its dependencies have already been moved to HEAD
2) if it depends on any package with a GCC tag, change those dependencies
to be *versioned* dependencies (for the new version in 10.2-gcc3.3),
and increase the version number of the current package by 10.
3) or if it has a GCC tag itself, increase its version number by 10
4) in either case 2 or 3, be sure that the package has a GCC tag, and
change its value to "GCC: 3.3"
5) test to make sure it compiles under gcc3.3
This is a bit tricky when there are different versions currently in stable
and unstable, for packages with GCC tags. When that happens, and another
package depends on the one with two tags, I'm making sure that the
dependent package not only has different versioned dependencies specified
in its stable and unstable versions, but (when necessary), I'm adding 20
rather than 10 to the revision number of the package in the unstable tree
(leaving it at +10 in the stable tree).
In practice, I'm doing this in reverse: moving things to HEAD, and then
going through and implementing versioned dependencies in all things that
depend on them (changing version numbers and GCC values at the same time).
I'm working on both the stable and unstable trees at the same time, so in
the end, we'll have a "stable" part of the 10.2-gcc3.3 distro which is just
the gcc3.3-update of the stable part of the 10.2 distro. Packages there
should probably get more testing before they are truly called stable, but
in this case the testing will need to come from fink developers. It's my
belief that we need to get an entire 10.2-gcc3.3 tree ready, and make a
bindist for it, before asking the majority of fink users to try the
upgrade.
--Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
