X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=RL3fIoRvtTme+2AR
	Kzq2+Cvve1uVhSclRb23EeQpeMYOepEIFnVL5mMy0DhT35p0ke1vv0Rw27vFpFXq
	RIvvicov0nKNB3GMohA+kxeutFRm4wsUkPZ93CvRgOc8EGOyA5ElTYCcSkLLSDQy
	a7Q2re76S1HA7g5RDnA+kvEG+9g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=7NxIO0NT4vwOu/5vyqFu/x
	fmVR8=; b=VnV0+IxbCF12vkWHdVTfwCAFDDcnGKs4sxBYjePRrOisPozX3EEVLB
	GhdClVfuHylZaUVBLQCiBtcfMPa3DIrjXI8IbwCt/fKURnmiPkoJ61ujnghGE8Ja
	uUa1gvlh1QEpHzWsr3eNR3nz+SYvaxaekcM16/cBXet4z5chad+tQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=exclusion, intalling, H*M:28a9, H*M:fa97
X-HELO: limerock02.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Subject: Re: How to "lock" package exclusion?
To: cygwin AT cygwin DOT com
References: <vriu60g0fl1q DOT fsf AT gavenkoa DOT example DOT com>
From: Ken Brown <kbrown AT cornell DOT edu>
Message-ID: <d41f23de-5220-fa97-28a9-0624e502d718@cornell.edu>
Date: Tue, 13 Jun 2017 10:12:08 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <vriu60g0fl1q.fsf@gavenkoa.example.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Cornell-Gauge: Gauge=XXXXX
X-PMX-CORNELL-AUTH-RESULTS: dkim-out=none;
X-IsSubscribed: yes

On 6/13/2017 2:39 AM, Oleksandr Gavenko wrote> How can I "lock" package 
to prevent intalling even if it is "required".

There's no supported way to do this, but you can try to trick setup into 
thinking a package is installed by editing /etc/setup/installed.db. 
You'll have to re-do this every time the package is updated.  And, of 
course, you might break something if it turns out that you really do 
need the package.

Ken


--
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