From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] astrometry.net-0.38-1
Date: Tue, 11 Oct 2011 10:19:00 -0000 [thread overview]
Message-ID: <4E94181D.1090600@gmail.com> (raw)
In-Reply-To: <4E8C7F4E.3080002@cwilson.fastmail.fm>
On 10/5/2011 6:01 PM, Charles Wilson wrote:
> On 10/4/2011 4:02 AM, Jussi Kantola wrote:
>
>> category: Science
>> requires: cairo libcairo2 python-cairo libnetpbm10 netpbm libpng14
>> libjpeg8 zlib zlib0 python python-numpy pkg-config cygwin
>> sdesc: "Astrometry.net astrometrical solver."
>> ldesc: "Astrometry.net analyses an astronomical image (photograph of the
>> night sky) to output, among other things, the central coordinate of the image,
>> the visible field of view, and the list of deep sky objects potentially
>> visible within the field."
>
> +1.
>
> However, as Corinna pointed out, there are some issues with the
> packaging. I'll take a look this weekend and come up with some
> suggestions for you.
>
> FYI, you probably don't need to list both "zlib" and "zlib0" as
> requires: (most packages need just the dll, in zlib0). Ditto for
> "cairo" and "libcairo2" -- you probably only need libcairo2. Also, it is
> no longer recommended to include 'cygwin' in the requires: list -- it is
> assumed that cygwin is a requirement for everything.
>
> --
> Chuck
>
+1 . Same comment about missing package procedure
This upstream package is not really thought for easy porting,
it inglobes a lot of library including gsl-1.14 while should be better
to link with cygwin gsl.
Regards
Marco
next prev parent reply other threads:[~2011-10-11 10:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 8:02 Jussi Kantola
2011-10-04 9:29 ` Corinna Vinschen
2011-10-05 8:43 ` Peter Li
2011-10-05 10:04 ` Jussi Kantola
2011-10-05 16:02 ` Charles Wilson
2011-10-11 10:19 ` Marco Atzeri [this message]
2011-10-18 11:21 ` Jussi Kantola
2011-10-18 11:49 ` Chris Sutcliffe
2011-10-18 21:12 ` Ken Brown
2011-10-20 8:19 ` Jussi Kantola
2011-10-30 21:10 ` Jussi Kantola
2011-11-03 12:03 ` Corinna Vinschen
2011-11-03 12:55 ` Charles Wilson
2011-11-03 13:03 ` Corinna Vinschen
2011-11-04 0:52 ` Jussi Kantola
2011-10-05 16:19 ` Andrew Schulman
2011-10-06 13:06 ` Jussi Kantola
2011-10-07 14:20 ` Marco Atzeri
2011-10-07 16:19 ` Jussi Kantola
2011-10-07 16:20 ` Jussi Kantola
2011-10-10 18:54 ` Jussi Kantola
2011-10-10 23:14 ` Christopher Faylor
2011-11-04 6:30 ` Charles Wilson
2011-11-04 9:02 ` Jussi Kantola
2011-11-04 15:12 ` Yaakov (Cygwin/X)
2011-11-04 16:08 ` Charles Wilson
2011-11-04 21:13 ` Charles Wilson
2011-11-07 13:18 ` Jussi Kantola
2011-11-07 14:46 ` Charles Wilson
2011-11-07 16:13 ` Jussi Kantola
2011-11-07 16:18 ` Christopher Faylor
2011-11-08 4:50 ` Charles Wilson
2011-11-08 7:19 ` Christopher Faylor
2011-11-08 12:44 ` Ken Brown
2011-11-09 2:43 ` Chris Sutcliffe
2011-11-09 10:00 ` Jussi Kantola
2011-11-09 23:24 ` Charles Wilson
2011-11-11 10:46 ` Jussi Kantola
2011-11-11 10:53 ` Jussi Kantola
2011-11-13 17:35 ` Jussi Kantola
2011-11-08 18:01 ` Marco Atzeri
2011-11-08 19:55 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E94181D.1090600@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).