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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=UQjzOr2NajgWdeywqyagBxOWyqzN5WcWXhKtKnOf2ox
	D0Gp6lRi5QresFGdLcWo5M0lOUuEc7GBuSw4r21J4zQgXfrOeQ+6jOxRzZiJpzbS
	hix05KGwzBrLz80no84wfCvWiEVWfrCDZbdeVf20DG2TJymaW5r1DS4/flMS+mHU
	=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=zQOHmDM2MO3+Kk1tFYRbpK6ixNs=; b=knho5a7VCgmKZt+1X
	sqE/J9zpfT5GCQ/tcaswOjEZ2l4U2dfOdBH9Ac9XV4pU+wkrG5NkN/DAjQZLoS1d
	oQMOS6qugZUqqGZdQ00IgmHz3RW6sJbAhgyPoJOhVmarQ7DcIXav0o44RDCI632J
	oJiWhE1cOW4IacmHpr3tpsNE0Q=
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=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPAM_URI,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-in-07.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-14.arcor-online.net 834EE9BE02
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: man-db-2.6.7-2
References: <announce DOT 53EDA004 DOT 7060207 AT cygwin DOT com>	<CAMKht8jp2tA1SLtXpSs1=ubrfTNQkpwzNUHW7omo0OF4=cvXuw AT mail DOT gmail DOT com>	<53EE1737 DOT 7080306 AT cygwin DOT com>	<CAMKht8jpQVfDhDorom24OiJ9YE07zBqjDSF5zVfWiFsdN1kaUg AT mail DOT gmail DOT com>
Date: Sat, 16 Aug 2014 08:11:01 +0200
In-Reply-To: <CAMKht8jpQVfDhDorom24OiJ9YE07zBqjDSF5zVfWiFsdN1kaUg@mail.gmail.com>	(Michael DePaulo's message of "Fri, 15 Aug 2014 18:15:27 -0400")
Message-ID: <874mxdezgq.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.91 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s7G6KmHw011242

Michael DePaulo writes:
> Consider the example of where I work. After I install the corporate IT
> department's SCCM "package"/"script" for Cygwin (1.7.16, last updated
> August 2012)

That is an entirely different issue and one your IT will have to
resolve.  Given how these departments operate, don't get your hope up
too high; they've already ticked all their checkboxes and moved on to
other things.

In my own installation I do an incremental rebase and will do a mandb
update each time setup has been run (I've patched setup.exe to allow for
that).  That's the only way to keep things sane at the moment if you're
doing installations for anyone but yourself, especially if some of those
user do not have local admin rights.

> I am greeted by this message every time I start the Cygwin Terminal:

That will soon become a non-issue with the AD integration that is in the
works.  Your IT department will have to update to it, though.

[…]
> I am not suggesting that users see a mandb message every time they
> launch cygwin. But I am suggesting that that users see it when they
> 1st launch cygwin. They already see this message:
[…]

In all these cases it's easy and fast to test for the condition that
triggers the message, that is quite necessary since that check will be
run on every login.  Checking for no database would be easy enough I
think, but checking for an outdated database might be more tricky.  I
could think up something to add to base-files for the first case.

I'm not sure what to do for the latter.  I think it must be the
responsibility of any package that installs man pages to trigger a db
update, but that would get us into the situation again that the first
install takes inordinately long on some systems (just to note that
TeXlive has that same problem).  We might need to cook up with some way
to defer these until they can be run in the background.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

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