On Thu, 2020-09-17 at 11:46 -0400, Ruben Safir wrote:
> I can do it. I used to do it all the time.
This is the right solution, then. I wish I could give you more direct
advice for how to remove the dependency, but I've been spoiled by
Portage: a simple config file change is all that's needed in that
system. Since you mentioned Artix, hopefully pacman's pkgbuild system
is equally as easy/straightforward.
> Why would vim need perl built in as a dependency.
I don't know, off-hand. Some searching didn't turn up a definitive
result either. It is an optional dependency, but the dependency is
build-time, not run-time, so I'm assuming it is used for some features
that are enabled by the vim package from the distribution. Most
systems will have packages depending on perl, so the package
maintainers think "the average vim user will have perl installed
anyway, so why not enable those optional features?"
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/b17cdb628c6e8d46f8d8c59b8c36924f79e50898.camel%40connell.tech.
No comments:
Post a Comment