On Mar 21, 2007, at 5:54 PM, Mark Duling wrote:
Sounds like we have a consensus for nuking. I'd say go ahead if
you want
to. If there are reasons down the road to have them, they can be
recreated at revision levels that actually work. Better than having
broken ports that confuse people.
Mar
Ryan Schmidt <[EMAIL PROTECTED]> on Wednesday, March 21, 2007 at
12:12 AM -0800 wrote:
>I'd say nuke it, along with pango-devel and glib2-devel. Should I do
>it? Sigh... I forget again: is there an easy way to tell if any ports
>depend on those?
>
>Unless... I mean, we could certainly update th
On Mar 21, 2007, at 9:12 AM, Ryan Schmidt wrote:
On Mar 20, 2007, at 23:25, Mark Duling wrote:
cairo-devel is ancient, broken, and looks unnceccesary now. The
tarball
is fetched from ~/pkern. Can it be deleted?
I'd say nuke it, along with pango-devel and glib2-devel. Should I
On Mar 20, 2007, at 23:25, Mark Duling wrote:
cairo-devel is ancient, broken, and looks unnceccesary now. The
tarball
is fetched from ~/pkern. Can it be deleted?
I'd say nuke it, along with pango-devel and glib2-devel. Should I do
it? Sigh... I forget again: is there an easy w
cairo-devel is ancient, broken, and looks unnceccesary now. The tarball
is fetched from ~/pkern. Can it be deleted?
Mark
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
