[63831] trunk/dports/graphics/InsightToolkit/Portfile

[Darren Weber]

Latest revision has disabled parallel builds in the port.

Interesting, did not know about the 'notes' facility.  As Ryan indicated,
the ui_msg is to advise users that the build and install will take a very
long time.

I agree that -o and -k are not commonly used by users, but I've found that
this port can fail during java wrapping near the very end of the build
process (due to lack of resources in the java-vm).  It's painful to start
all over again, so my hope is that -o and -k will help to recover a build
failure.  Is there a better way of recovery from a build failure?  Perhaps
suggesting that users progress in steps, e.g.:

$ sudo port -d configure InsightToolkit {variants}
$ sudo port -d build InsightToolkit {variants}
$ sudo port -d destroot InsightToolkit {variants}
$ sudo port -d install InsightToolkit {variants}

(Perhaps leave out the destroot and go from build to install?)  If it fails
in the build phase, yet it got about 90% complete, would it keep the current
build results if you ran the build phase again?  e.g.:

$ sudo port -d configure InsightToolkit {variants}
$ sudo port -d build InsightToolkit {variants}
$ # Oh, shoot!  It failed at 90% complete.
$ sudo port -d build InsightToolkit {variants}
$ # Phew!  It picked up where it left off and completed - yipee.
$ sudo port -d destroot InsightToolkit {variants}
$ sudo port -d install InsightToolkit {variants}

TIA,
Darren




On Tue, Feb 16, 2010 at 7:41 PM, Ryan Schmidt <ryandesign at macports.org>wrote:

>
> On Feb 16, 2010, at 18:26, Jeremy Lavergne wrote:
>
> > Please consider notes instead of ui_msg.  This allows the user to see
> what your port was remarking without having to reinstall every time they'd
> like to see the message.
>
> I think part of Darren's purpose in doing this in post-extract instead of
> notes is that he's advising the user it will take a long time to build.
> Notes are not shown until the port has finished installing, and are thus not
> a helpful place to display that kind of advice.
>
> The information about turning off parallel build should go away; if the
> port doesn't work with parallel building, then the port should specify
> "use_parallel_build no" and be done with it. -o and -k are flags port
> developers are expected to use on occasion, but users should not be expected
> to need to use, and ports probably don't have any reason to suggest their
> use to users.
>
>
> > On Feb 16, 2010, at 3:48 PM, dweber at macports.org wrote:
> >
> >> Revision63831Authordweber at macports.orgDate2010-02-16 12:48:09 -0800
> (Tue, 16 Feb 2010)Log Message
> >> Added ui_msg to warn about build duration and possible build problems
> with parallel make jobs
> >> Modified Paths
> >>      • trunk/dports/graphics/InsightToolkit/Portfile
> >> Diff
> >> Modified: trunk/dports/graphics/InsightToolkit/Portfile (63830 => 63831)
> >>
> >> --- trunk/dports/graphics/InsightToolkit/Portfile    2010-02-16 15:27:07
> UTC (rev 63830)
> >> +++ trunk/dports/graphics/InsightToolkit/Portfile    2010-02-16 20:48:09
> UTC (rev 63831)
> >> @@ -86,6 +86,14 @@
> >> post-extract {
> >>     move ${workpath}/InsightToolkit-${version} ${worksrcpath}
> >>     move ${workpath}/CableSwig-ITK-${version}
>  ${worksrcpath}/Utilities/CableSwig
> >> +    ui_msg "***************************************************"
> >> +    ui_msg "InsightToolkit is a very long config/build process."
> >> +    ui_msg "It can take several hours, even on a fast system."
> >> +    ui_msg "Also, it may fail due to parallel make jobs, so"
> >> +    ui_msg "try the 'build.jobs=1' option and run the build"
> >> +    ui_msg "many times until completion.  The -o and -k options"
> >> +    ui_msg "may be useful too, see man port for details."
> >> +    ui_msg "***************************************************"
> >> }
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20100217/625e46da/attachment.html>