This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Proposal to add and maintain the epstool package

On Fri, Jan 07, 2005 at 02:41:37PM -0800, wrote:
>--- Christopher Faylor <> wrote:
>> The format of setup.ini is easy enough to understand.  You don't need a
>> special program to test this.
>OK, you have to use unix style path separators - I figured that out, so
>setup.ini parses successfully.
>I got the file sizes and the md5's right.
>I still have a couple problems.
>The first is that the package doesn't reliably show up as installable after
>setup.ini is parsed.  Sometimes it does, but I haven't been able to figure out
>what combination of factors succeeds here.  Most of the time, it doesn't show
>up .
>Then secondly, when it does show up as installable, I get an error message
>about not being able to open (null) when the install is attempted.  Not clear
>on what is causing that. The installation fails, and then if the attempt is
>repeated, it does not show up as installable.
>My setup.ini is as follows:
># This file is automatically generated.  If you edit it, your
># edits will be discarded next time the file is generated.
># See for details.
>setup-timestamp: 1105134997
>@ epstool
>sdesc: "Edit preview images and fix bounding boxes in EPS files"
>ldesc: "Edit preview images and fix bounding boxes in EPS files
>Encapsulated PostScript (EPS) files may contain a preview to be used
>by programs that can't interpret the PostScript code. epstool can
>create and extract such previews. epstool can also calculate an optimal
>bounding box for an EPS file."
>category: Graphics
>requires: cygwin
>version: 3.06-1
>install: release/epstool/epstool-3.06-1.tar.bz2 146825
>source: release/epstool/epstool-3.06-1-src.tar.bz2 189756
>I'm not certain of the correct way to generate the timestamp.  This might be
>part of the problem?  Pointers appreciated.

The timestamp probably isn't even absolutely required but you could
always use whatever is currently in your setup.ini file.

Otherwise, the above looks good to me, assuming that you're putting the md5sum
on the same line as the filename and file size.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]