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 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? I trust there are other packages like this.
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 10.4.9 and 2.4.0), so gcc-5363 is the latest. gcc-3.3 is needed for Panther, which is still supported AFAIK... (although that might change next week or something, with Leopard) --anders
*On Thu, 18 Oct 2007 17:03:06 +0200 * Anders F Björklund <afb@macports.org> 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 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 10.4.9 and 2.4.0), so gcc-5363 is the latest.
gcc-3.3 is needed for Panther, which is still supported AFAIK... (although that might change next week or something, with Leopard)
Thanks for your explanation. I used wrong package as example. I dont suggest to remove apple-gcc in fact. I mean to clean up packages like tin-devel, which is definitely outdated. Another example is emacs-devel 22.0.97. With Emacs 22.1 released this package is outdated and may confuse users of macports.
On 10/18/07, CHENG Gao <chenggao@gmail.com> 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 outdated and useless.
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?
I trust there are other packages like this.
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 contacted the maintainer or tried to update the port yourself? -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@mac.com>
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 contacted the maintainer or tried to update the port yourself?
Not really. This wont trouble me. For the apps I need, I'll search ports first. If there is I'll install from port tree; if it's not up to date, I'll try to figure out update or install from source. In fact I submitted update for bogofilter and gnupg2. My question is more about port policy. Anyway it does not matter that much.
participants (3)
-
Anders F Björklund
-
CHENG Gao
-
paul beard