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
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: man-db-2.6.7-2
References: <announce.53EDA004.7060207@cygwin.com>	<CAMKht8jp2tA1SLtXpSs1=ubrfTNQkpwzNUHW7omo0OF4=cvXuw@mail.gmail.com>	<53EE1737.7080306@cygwin.com>	<CAMKht8jpQVfDhDorom24OiJ9YE07zBqjDSF5zVfWiFsdN1kaUg@mail.gmail.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

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