From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2073 invoked by alias); 6 Oct 2016 18:22:59 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 2064 invoked by uid 89); 6 Oct 2016 18:22:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=BAYES_05,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=lying, Gratz, H*r:192.168.3, gratz X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 06 Oct 2016 18:22:57 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id u96IBeld038875 for ; Thu, 6 Oct 2016 11:11:42 -0700 Message-ID: <57F6966E.4050303@tlinx.org> Date: Thu, 06 Oct 2016 18:30:00 -0000 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Blocking a base package from installing References: <878tu1qtes.fsf@Rainer.invalid> In-Reply-To: <878tu1qtes.fsf@Rainer.invalid> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00075.txt.bz2 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