Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 28 Nov 2003 21:13:26 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com, "David A. Cobb" Subject: Re: Info and Document Path In-Reply-To: <3FC63F13.6010607@cox.net> Message-ID: References: <3FC63F13 DOT 6010607 AT cox DOT net> Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 27 Nov 2003, David A. Cobb wrote: > I googled about looking for an answer, all I see is a very short thread > between Chuck and Chris on > . > > Is the policy that documentation and info is moving into /usr/share/...? > If yes, is there any ongoing process of moving things out of /usr/doc? > As things stand, it isn't easy to know where to look! And my $INFOPATH > is probably abgevukkett. > > Thanks, Well, basically maintainers are encouraged to have the documentation in /usr/share/doc in any newly uploaded package. It's up to the maintainers to decide when they are updating the packages. Also, some packages that probably won't have any updates to them (e.g., compatibility packages) are likely to keep their documentation in /usr/doc (I don't know what the policy is on those). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/