cairo-devel is ancient, broken, and looks unnceccesary now. The tarball is fetched from ~/pkern. Can it be deleted? Mark
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 way to tell if any ports depend on those? Unless... I mean, we could certainly update them to glib 2.13.0, and pango 1.17.0 and cairo 1.5.0 when they're available. But I don't know what would require those devel versions. The latest stable versions of each are really pretty good, as far as I can tell.
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 do it? Sigh... I forget again: is there an easy way to tell if any ports depend on those?
yes, there is: $grep :cairo-devel */*/Portfile graphics/pango-devel/Portfile:depends_lib port:glib2-devel port:cairo-devel $grep :glib2-devel */*/Portfile graphics/pango-devel/Portfile:depends_lib port:glib2-devel port:cairo-devel $grep :pango-devel */*/Portfile so as long as all three of them are nuked (which sounds like a good idea) there's no problem Regards, Elias
Ryan Schmidt <ryandesign@macports.org> 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 them to glib 2.13.0, and pango 1.17.0 and cairo 1.5.0 when they're available. But I don't know what would require those devel versions. The latest stable versions of each are really pretty good, as far as I can tell.
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. Mark
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.
Mark
I've removed them from the tree in r23002. Regards, Elias
I forget again: is there an easy way to tell if any
ports depend on those?
yes, there is:
$grep :cairo-devel */*/Portfile
I'll put this in the FAQ. Would it be useful to make the port command do this in a future revision? Mark
On Mar 26, 2007, at 6:58 PM, Mark Duling wrote:
I forget again: is there an easy way to tell if any
ports depend on those?
yes, there is:
$grep :cairo-devel */*/Portfile
I'll put this in the FAQ. Would it be useful to make the port command do this in a future revision?
Mark
Yes, I that'd be a good idea. Regards, Elias
participants (3)
-
Elias Pipping
-
Mark Duling
-
Ryan Schmidt