Hi,
I did that for multiple reasons.
First of all, I felt +aqua didn't qualify as a mere variant.
It's a hack that goes so far, that vim -aqua and vim +aqua
can be regarded as two different ports.
For instance, vim +aqua doesn't come with vimdiff, vimtutor,
etc.
Even more importantly the vim folder ${prefix}/share/vim/...
does not come with vim +aqua, instead that folder is located
at
/Applications/MacPorts/Vim/Vim.app/Contents/Resources/vim/runtime
(iirc)
So, in comparison, if e.g. the +no_prefix or whatever it's
called now variant that gnu ports like findutils have, *only*
installed 'find' (and the like) instead of 'gfind and find',
it would make depending upon findutils very difficult,
because there'd never be a path one could be sure 'find' can
be found at given the port has been installed.
The same is true for vim +aqua / vim -aqua. There needs to be
a path the vim folder can be found at, always, no matter what
variants have been applied.
Furthermore, bumping vim is not a problem. The new patches
apply cleanly. However, with vim-app i.e. there's the macatsui
variant which consists of a patch that breaks pretty much with
every new patch. Bumping vim shouldn't be delayed for a variant
that's only a subvariant of +aqua.
Some people raised the concern that having to install both
vim and vim-app now, if one wants both a console vim and
a gvim (although technically, console vim *can* be accessed
via
/Applications/MacPorts/Vim/Vim.app/Contents/MacOS/Vim
), one'd have to install the vim folder twice, which takes
up 20MB.
On the other hand, I have to say I no longer really care. I
still consider having split up vim into two ports a good
decision, however, if there's concensus, merging vim-app,
back in, go ahead - all the ports i maintain are openmaintainer.
Kind regards,
Elias
On Jun 15, 2007, at 10:38 AM, Ryan Schmidt wrote:
On Jun 15, 2007, at 03:04, Emmanuel Hainry wrote:
I wonder why, but the aqua variant has been removed from vim and a
new
vim-app port has been created. One problem I have: it does not
contain
the non-gui vim, which a simple link makes available... Maybe vim-app
could have a variant for terminal vim. Second (possible) problem,
this
vim-app installs the gvim script (which I am very happy about), which
means vim-app can conflict with vim +gtk2 or whatever graphical
variant
you choose for vim. Third problem: two different ports, two different
maintainers, two instances of vim which are not in sync: vim-app is
7.1.000, vim is 7.1.002.
I preferred the way it used to be.
I see this was done in this revision:
http://trac.macosforge.org/projects/macports/changeset/23756
But Elias didn't say in the log message why it was done.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
