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=NRvQVmrFt/fO+D+v
	2sOdpiBgUlnn0eH+olLfgsvDVf7TlwBgocYt21SW+OkJ0BGZ5abc+w2J+rLhfaiR
	hjTuRcnmq35dS1yMGme+7JJWRHnMMRJyX6bVq4bm9JLRSzKYZsswQfATd8eL29fF
	NmmcaPtAWtZVZ+YaaFFohN2MX4E=
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=PkNjv25DyqFvgsW27LBhaY
	yszdk=; b=l//w7hh5WnIaAPBYOolJ66sAhITsCnsuMUkO870YvAbLGlMluh+pBj
	kAvWE5RvCsjGSY9fZc1O0OVwZUpYwyRV0ftOmZAMMA5zY+2eiOEjb3Q5G9hiaju8
	GcgPgUFaUM40sGxng7KpfsBoMmawGNSh3puHL7/WkpoAUxeSMIBio=
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=-3.1 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*MI:sk:57F6E72, H*f:sk:57F6E72, H*i:sk:57F6E72, designated
X-HELO:	mailout11.t-online.de
Subject:	Re: Blocking a base package from installing
To:	cygwin AT cygwin DOT com
References:	<CAGHJv4cPr2Pe31nBg+KZ1nbODGtb977NOxOHgXyd89xEY2uh0g AT mail DOT gmail DOT com> <878tu1qtes DOT fsf AT Rainer DOT invalid> <57F6966E DOT 4050303 AT tlinx DOT org> <874m4pqp27 DOT fsf AT Rainer DOT invalid> <57F6E725 DOT 9090001 AT tlinx DOT org>
From:	=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID:	<ce4af242-0885-5779-cc60-02b5a01c53ea@t-online.de>
Date:	Fri, 7 Oct 2016 13:02:57 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version:	1.0
In-Reply-To:	<57F6E725.9090001@tlinx.org>
X-IsSubscribed:	yes

Am 07.10.2016 um 02:07 schrieb Linda Walsh:
> Achim Gratz wrote:
>> Now, that last question of yours: No, the package manager should never
>> allow you to not install a base package.  These are in category "Base"
>> precisely so the rest of the system can rely on the functionality
>> provided.
> ---
>     And what other programs will stop functioning if vim is not installed?

Vi is, for better or for worse, the default/fall-back system editor.  It 
is assumed to be there by every useful definition of what "Unix" is. 
The possibilities for things breaking if it's not there are therefore 
almost endless.

>     If I compile and install a version of vim on my system, why would I
> want to put it in a location like /usr/local where
> it might not be used -- all the time?

Because /usr/local is the designated location for software that's not 
part of the organized software distribution.  If you want to build your 
own, /usr/local is where it's supposed to go --- or $HOME if you don't 
have admin privileges.

Unix does have a very different approach to installing programs compared 
to Windows, in that it collects files from various packages in a few 
central places: /usr/bin, /usr/etc, /etc, and so on.  That approach 
requires consistent organization to avoid complete chaos.  Distributions 
like Cygwin provide that organization.  You mess with that at your own 
peril.  That's why non-distribution software gets its own area to work 
in: /usr/local.

>     I'm the only user on my system -- whether I run as a user
> or as root, or whatever, I'm not doing this for someone else.

Did it occur to you that the system really has to support much more 
varied use cases than your own particular corner case?

> If I try to edit a file using 'vim' from the explorer menu, will it
> invoke my vim in /usr/local -- of course not.

If you do set up such an explorer menu entry, it'll do whatever you tell 
it to.  It'll only end up "of course not" working if you "of course" 
configure things differently than you actually wanted to.  But why would 
anyone do that?

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

- Raw text -