port vim-app fails

[pengyu.ut@…]

Please see the attached log file for further info.

[pengyu.ut@…]

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_vim-app/vim-app/main.log

[cooljeanius (Eric Gallager)]

vim-app is only for old OSes. Since you're on Mountain Lion, you should try MacVim instead.

[ryandesign (Ryan Carsten Schmidt)]

The log doesn't show any build failure, only an archive fetch failure. Perhaps you have MacPorts configured to use archives only? If so that's not surprising.

If you allow MacPorts to try to build it, you should see something like:

$ sudo port install vim-app
--->  Computing dependencies for vim-app
--->  Fetching distfiles for vim-app
[snip]
--->  Attempting to fetch 7.3.760 from http://distfiles.macports.org/vim/7.3_2
--->  Attempting to fetch 7.3.761 from http://distfiles.macports.org/vim/7.3_2
--->  Attempting to fetch 7.3.762 from http://distfiles.macports.org/vim/7.3_2
--->  Attempting to fetch app-bm.tar.gz from http://distfiles.macports.org/vim/7.3_2
--->  Attempting to fetch doc.tar.gz from http://distfiles.macports.org/vim/7.3_2
--->  Verifying checksum(s) for vim-app
--->  Extracting vim-app
--->  Applying patches to vim-app
--->  Configuring vim-app
Error: vim-app does not run on Mac OS X 10.6 or greater. Please use MacVim instead.
Error: org.macports.configure for port vim-app returned: incompatible Mac OS X version
Please see the log file for port vim-app for details:
    /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_editors_vim-app/vim-app/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port vim-app failed
$ 

Which makes me think the message should really be printed in pre-fetch not pre-configure; no need to make the user fetch a bunch of files if the user won't be able to use them anyway.

[raimue (Rainer Müller)]

I switched the message to pre-fetch in r109612. As I did find the original problem in the log provided I am calling this issue fixed as well with this change.