I think macports tree needs cleanup. For example, there are new/tin
(1.8.1), news/tin-devel (1.7.10) and news/tin-current (1.9.2). In fact
the latest stable release is 1.8.3 and current release is 1.9.2, so
devel version 1.7.10 is obviously outdated and useless.
Another example is apple-gcc. Tree
CHENG Gao wrote:
Another example is apple-gcc. Tree has apple-gcc33 build 1819, and
apple-gcc40 build 5363, while latest Tiger 10.4.10 has build 5367.
Should they be updated? Or even apple-gcc33 be removed?
Apple has not released the source code for Mac OS X 10.4.10 or
Xcode 2.4.1 (only
*On Thu, 18 Oct 2007 17:03:06 +0200
* Anders F Björklund [EMAIL PROTECTED] climbed out of the dark hell and cried
out:
CHENG Gao wrote:
Another example is apple-gcc. Tree has apple-gcc33 build 1819, and
apple-gcc40 build 5363, while latest Tiger 10.4.10 has build 5367.
Should they be
On 10/18/07, CHENG Gao [EMAIL PROTECTED] wrote:
I think macports tree needs cleanup. For example, there are new/tin
(1.8.1), news/tin-devel (1.7.10) and news/tin-current (1.9.2). In fact
the latest stable release is 1.8.3 and current release is 1.9.2, so
devel version 1.7.10 is obviously
On a theoretical level, this makes sense and would be best addressed
on a port by port basis. On a practical level, it's probably a
function of available time and feedback from users that new versions
are out and in wider adoption.
If there are ports that particularly trouble you, have you
