From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Blocking a base package from installing
Date: Thu, 06 Oct 2016 18:30:00 -0000 [thread overview]
Message-ID: <57F6966E.4050303@tlinx.org> (raw)
In-Reply-To: <878tu1qtes.fsf@Rainer.invalid>
Achim Gratz wrote:
> Chris Sutcliffe writes:
>> 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?
>
> Yes, at least two.
>
> 1. Build a proper package and give it a higher version number than
> Cygwin's own Vim.
>
> 2. Fake the installation of vim-minimal in /etc/setup/installed.db and
> give that fake installation some high version number.
---
Both of which are "lying" to the package manager, to get it to
NOT install an inferior (from the standpoint of not containing
the user-desired modifications/features) package. It should
be possible to "LOCK" a package (base or not), to prevent it from
being removed/updated/installed or changed by setup, no?
--
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 18:22 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
2016-10-06 17:37 ` Achim Gratz
2016-10-06 18:30 ` Linda Walsh [this message]
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=57F6966E.4050303@tlinx.org \
--to=cygwin@tlinx.org \
--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).