Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Fri, 5 Sep 2003 15:07:47 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Sam Steingold <sds AT gnu DOT org>
cc: cygwin AT cygwin DOT com
Subject: Re: setup.hint / ldesc
In-Reply-To: <u7k4n6v63.fsf@gnu.org>
Message-ID: <Pine.GSO.4.56.0309051505460.7348@slinky.cs.nyu.edu>
References: <u7k4n6v63 DOT fsf AT gnu DOT org>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 5 Sep 2003, Sam Steingold wrote:

> RPM *.spec lets me include the summary from an external file:
>
> %description
> %(cat SUMMARY)
>
> can I do something similar with setup.hint/ldesc?
> I don't want to duplicate the same information twice.

No, you can't.  However, you can create a "setup.hint.in" with such syntax
and process it to create the actual "setup.hint" during your package build
process.  I'm assuming you'd like to package some application which
contains the description in a file that's changed relatively often.
	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/