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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=jaJ//XpN/76xKhni6CyeTrbiGmTuc62a1jTgMyf9FHX
	uiy8xOosqlsZ92vuwqNGqvEDbWrJN4sOxdp1aId9fiG14ATAYG9AutyOOH8/UoX1
	VqtUJhemyG5jTGUty0sJuEbUrkoH6fsenDwpxM8aaTScnEQQEBgfPUiWujAbqXGw
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=1SaBLekvaS3y3HJFdFWLAOVPw84=; b=ha1ZwAeqnfHG8QWBH
	oA8232uq2CXHbW90/0OsZc+0qwnim5zBcNc+7sUq+1axjmUCtnjK3L2P7jifx1io
	W5J7WG362O5Y/0Sr620Fh0ymjufa1K5psAl5dX7HHNA3yinABg9m5/763HYAQ+63
	JuoyAfn5Owwm5tH4nxk994PlYA=
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=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	limerock01.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<54E39493.9090706@cornell.edu>
Date:	Tue, 17 Feb 2015 14:20:51 -0500
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Texlive Package Problem
References:	<54E38496 DOT 9020500 AT w5pny DOT com> <54E38E53 DOT 4020906 AT cornell DOT edu> <87h9uks6n1 DOT fsf AT Rainer DOT invalid>
In-Reply-To:	<87h9uks6n1.fsf@Rainer.invalid>
X-IsSubscribed:	yes

On 2/17/2015 2:02 PM, Achim Gratz wrote:
> Ken Brown writes:
>> There's no problem here.  /var/lib/texmf/postinstall is used for the
>> new streamlined TeX Live postinstall process.  The files in it are
>> markers indicating that something needs to be done, and they are
>> renamed with ".done" appended when it's done.  The same thing is done
>> with normal postinstall files in /etc/postinstall, but I guess
>> cygcheck knows about them.
>
> You could create the marker files in the normal postinstall phase via
> script and remove them when you're done.  That way they wouldn't be
> packaged and cygcheck would not complain if they're missing.  This is
> however a lot less elegant unless cygport could be enhanced to provide
> the boilerplate wrappers for that.
>
>> I don't know if there's something I should do to avoid this problem or
>> if cygcheck just needs to be tweaked.
>
> That would be the other option, but I don't know how hard that would be.
> If it's already matching on "/etc/postinstall" to do that deed then it
> might be a small change to simply just check for
> ".*/postinstall/<script>.done"

It is already matching on /etc/postinstall; see 
winsup/utils/dump_setup.cc:check_package_files().  Corinna, what do you 
think?

Ken


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