X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4AB77567.2090108@cwilson.fastmail.fm>
Date:	Mon, 21 Sep 2009 08:45:27 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: rogue file in /etc/postinstall after update?
References:	<4AB7091E DOT 6040200 AT veritech DOT com>
In-Reply-To:	<4AB7091E.6040200@veritech.com>
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

Lee D. Rothstein wrote:
> why are th e following files left in /etc/postinstall after each
> update/reinstall or initial install?:
> 
> gcc-mingw-ada-3.4.4-20050522-1.tgz
> gcc-mingw-core-3.4.4-20050522-1.tgz
> gcc-mingw-g++-3.4.4-20050522-1.tgz
> gcc-mingw-g77-3.4.4-20050522-1.tgz
> gcc-mingw-gdc-3.4.4-0.12.1.tgz
> gcc-mingw-gpc-3.2.3-20040516.tgz
> gcc-mingw-java-3.4.4-20050522-1.tgz
> gcc-mingw-objc-3.4.4-20050522-1.tgz
> 

They are not "rogue" files. That's how the gcc-mingw* packages WORK.
See: /etc/postinstall/gcc-mingw-*:

#!/bin/sh
[ -f /etc/postinstall/gcc-mingw-core-3.4.4-20050522-1.tgz ] || exit 0
[ -d /usr/include ] || exit 0
/bin/mkdir -p /usr/i686-pc-mingw32 /usr/include/mingw /usr/lib/mingw
/usr/i686-pc-cygwin/bin
cd /usr/i686-pc-mingw32
[ ! -e /usr/i686-pc-mingw32/include -a -d "../include/mingw" ] && ln -s
"../include/mingw" /usr/i686-pc-mingw32/include
[ ! -e /usr/i686-pc-mingw32/lib -a -d "../lib/mingw" ] && ln -s
"../lib/mingw" /usr/i686-pc-mingw32/lib
[ ! -e /usr/i686-pc-mingw32/bin -a -d "../i686-pc-cygwin/bin" ] && ln -s
"../i686-pc-cygwin/bin" /usr/i686-pc-mingw32/bin
echo "*** Unpacking
/etc/postinstall/gcc-mingw-core-3.4.4-20050522-1.tgz.  Please wait. ***"
/bin/tar -xzvf /etc/postinstall/gcc-mingw-core-3.4.4-20050522-1.tgz -C
/usr > /etc/preremove/gcc-mingw-core-manifest.lst



5 seconds of research would have answered your question.  But don't
worry. As soon as gcc-4.4.x for cygwin goes live, Dave plans to release
a true cross compiler for mingw, so the "gcc-mingw-*" packages will no
longer be structured in this way.

--
Chuck

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