[MacPorts] #38165: NERD_tree update to 4.2.0
#38165: NERD_tree update to 4.2.0 --------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: NERD_tree --------------------+-------------------------------- NERD_tree could use an update, and perhaps a revisit on its name. -- Ticket URL: <https://trac.macports.org/ticket/38165> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38165: NERD_tree update to 4.2.0 ------------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: NERD_tree | ------------------------+-------------------------------- Changes (by snc@…): * cc: raimue@… (added) -- Ticket URL: <https://trac.macports.org/ticket/38165#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38165: NERD_tree update to 4.2.0 ------------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: NERD_tree | ------------------------+-------------------------------- Comment (by raimue@…): Actually, I don't see much of a point in making ports for vim plugins. From an end-user view, do you really want to install them system-wide forcing them upon all users on your system? I would recommend to use either [https://github.com/tpope/vim-pathogen pathogen] or [https://github.com/gmarik/vundle Vundle] for handling of plugins in your home directory. The latter even has a integrated update functionality. -- Ticket URL: <https://trac.macports.org/ticket/38165#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38165: NERD_tree update to 4.2.0 ------------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: NERD_tree | ------------------------+-------------------------------- Comment (by snc@…): Agreed, and I use pathogen. But since this port already exists I figured it should get updated. Should we remove it instead? -- Ticket URL: <https://trac.macports.org/ticket/38165#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38165: NERD_tree update to 4.2.0 ------------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: NERD_tree | ------------------------+-------------------------------- Comment (by raimue@…): Replying to [comment:3 snc@…]:
Should we remove it instead?
Yes, that would be my suggestion. -- Ticket URL: <https://trac.macports.org/ticket/38165#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38165: NERD_tree update to 4.2.0 ------------------------+-------------------------------- Reporter: snc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: NERD_tree | ------------------------+-------------------------------- Comment (by deesto@…): Replying to [comment:4 raimue@…]:
Replying to [comment:3 snc@…]:
Should we remove it instead?
Yes, that would be my suggestion.
Despite the suggestion of 19 months ago, this port persists, and in its old version and port name: the latest source version is from 2011, and the ports version is one version behind even that. -- Ticket URL: <https://trac.macports.org/ticket/38165#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts