Opened 11 years ago

Closed 11 years ago

#40071 closed update (fixed)

vim/vim-app @7.3.762_2, MacVim @7.3.snapshot66_3: update to 7.4 (MacVim snapshot 70)

Reported by: larryv (Lawrence Velázquez) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: christianlaustsen@…, cooljeanius (Eric Gallager), g5pw (Aljaž Srebrnič), nonstop.server@…, dcecchin@…
Port: vim MacVim vim-app

Description

Vim 7.4 stable has been released. I’ll provide a patch later today or tomorrow, unless you already have something cooking.

Change History (10)

comment:1 Changed 11 years ago by christianlaustsen@…

Cc: christianlaustsen@… added

Cc Me!

comment:2 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:3 Changed 11 years ago by g5pw (Aljaž Srebrnič)

Cc: g5pw@… added

Cc Me!

comment:4 Changed 11 years ago by raimue (Rainer Müller)

Status: newassigned

I will definitely get to this, need to catch up with some other stuff first. For new stable releases I tend to test the different variants more thoroughly.

comment:5 in reply to:  4 Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to raimue@…:

I will definitely get to this, need to catch up with some other stuff first. For new stable releases I tend to test the different variants more thoroughly.

Sounds good. I worked a bit on vim, if you want to take a look.

  • A couple of patches have been obsoleted by upstream fixes. Notably, the configure script seems to respect CC now.
  • At least one Python variant (python27) fails to produce a correctly-linked vim due to the configure script incorrectly using LINKFORSHARED. I fixed the build by using pythonX.Y-config instead, but I didn’t kick the tires.
  • Even with the existing patch, the configure script finds the wrong Tcl unless --with-tclsh is used.

comment:6 Changed 11 years ago by nonstop.server@…

Cc: nonstop.server@… added

Cc Me!

comment:7 Changed 11 years ago by dcecchin@…

Cc: dcecchin@… added

Cc Me!

comment:8 Changed 11 years ago by raimue (Rainer Müller)

Thanks a lot for your work, Larry! First batch of changes from your branch landed in r110123. However, it's not the upgrade to 7.4 yet.

By the way, I did not use the same file for +python2x and +python3x as with a selection of both at the same time, the patch phase fails trying to apply the same patch twice (patchfiles-append does not ensure the list is unique).

comment:9 in reply to:  8 Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to raimue@…:

Thanks a lot for your work, Larry! First batch of changes from your branch landed in r110123.

Great!

By the way, I did not use the same file for +python2x and +python3x as with a selection of both at the same time, the patch phase fails trying to apply the same patch twice (patchfiles-append does not ensure the list is unique).

Ah, I hadn’t even considered trying those variants at the same time. Makes sense.

comment:10 Changed 11 years ago by raimue (Rainer Müller)

Resolution: fixed
Status: assignedclosed

Updates committed in r111449 and r111451.

Note: See TracTickets for help on using tickets.