This is the mail archive of the
mailing list for the Cygwin project.
Re: Proposal to add and maintain the epstool package
- From: <antiskid56-cygwin at yahoo dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 7 Jan 2005 14:41:37 -0800 (PST)
- Subject: Re: Proposal to add and maintain the epstool package
- Reply-to: antiskid56-cygwin at yahoo dot com
--- Christopher Faylor <firstname.lastname@example.org> 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
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 http://cygwin.com/setup.html for details.
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."
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.
James R. Phillips
South Bend, Indiana