From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Blocking a base package from installing
Date: Thu, 06 Oct 2016 17:28:00 -0000 [thread overview]
Message-ID: <3e621a89-f4e3-ee04-f7a1-4fd7312a1a18@t-online.de> (raw)
In-Reply-To: <CAGHJv4cPr2Pe31nBg+KZ1nbODGtb977NOxOHgXyd89xEY2uh0g@mail.gmail.com>
Am 06.10.2016 um 16:57 schrieb Chris Sutcliffe:
> I'm using a self compiled vim, so I uninstalled vim-minimal. Every
> time I run setup to get the latest updates, setup attempts to
> reinstall vim-minimal - is there a way to make setup ignore
> vim-minimal?
With the alternative being to pick a fight with the tools, wouldn't it
be a whole lot more straightforward to install your own vim with
--prefix $HOME or /usr/local instead? That's what I do with basically
all packages I install from sources; and using stow to manage them even
makes that reasonably painless.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-10-06 17:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 17:15 Chris Sutcliffe
2016-10-06 17:28 ` Hans-Bernhard Bröker [this message]
2016-10-06 17:37 ` Achim Gratz
2016-10-06 18:30 ` Linda Walsh
2016-10-06 18:35 ` Eric Blake
2016-10-06 19:15 ` Achim Gratz
2016-10-07 0:16 ` Linda Walsh
2016-10-07 11:04 ` Andrey Repin
2016-10-07 22:40 ` intelligent following of directions, or following them by rote Linda Walsh
2016-10-08 18:45 ` Brian Inglis
2016-10-09 6:56 ` Linda Walsh
2016-10-09 4:35 ` Erik Soderquist
2016-10-09 8:55 ` Linda Walsh
2016-10-07 22:04 ` Blocking a base package from installing Hans-Bernhard Bröker
2016-10-08 14:45 ` Linda Walsh
2016-10-06 19:02 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e621a89-f4e3-ee04-f7a1-4fd7312a1a18@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).