On 17/mag/08, at 21:26, Alakazam wrote: > If we agree that that is the correct solution for octave-forge, I can > look into this in the next couple of days.
I'm not sure how to cope with portgroups (they have to be builtin into macports from what I've read). I wrote a small script to parse web page and generate Portfiles with dependencies. I have still to try them all though, the few I checked supported DESTDIR so they should be fine. I octave-forge packages are going with portgroups I won't commit them, basically having a common set of properties is what I made, using a prototype Portfile and changing only per-package specific data. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
