From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] astrometry.net-0.38-1
Date: Mon, 07 Nov 2011 16:18:00 -0000 [thread overview]
Message-ID: <20111107161723.GB4738@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4EB7EF3D.8090004@cwilson.fastmail.fm>
On Mon, Nov 07, 2011 at 09:46:21AM -0500, Charles Wilson wrote:
>On 11/7/2011 8:18 AM, Jussi Kantola wrote:
>> On Fri, Nov 4, 2011 at 11:13 PM, Charles Wilson wrote:
>>> You should probably do that, to ensure that the build procedure works on
>>> your machine. Also, to test the resuts; I have no idea how to use this
>>> stuff.
>>
>> It builds fine, and the resulting installation works fine when I put
>> some sky catalogs in /usr/share/astrometry/data/.
>
>Good news. Please post *your* rebuilt packages somewhere, so they can
>be uploaded.
>
>> The question
>> becomes, would it be better to create a separate package
>> (astrometry.net-data-tycho or such) for the (example/test) catalogs,
>> than to have them in the binary/source packages? Theoretically, and I
>> suppose in eventual actuality as well, there could be many different
>> sets of catalogs, so separate packaging sounds like the way to go ...
>
>Definitely separate. However, it may be best not to create any catalog
>packages at all, and instead provide helper scripts (in
>/usr/lib/astrometry/scripts/ ?) to d/l and install the individual
>catalogs. The reason for this suggestion is twofold.
>
>First, if you create a cygwin package containing the data from catalog
>"foo", then cygwin will be *redistributing* that data. However, many
>scientific databases of this sort, while free (gratis) to use, prohibit
>redistribution -- everybody is required to get them directly from the
>source. So, for this sort of catalog, a helper script to enable the
>end-user to do THAT is the only solution.
>
>Second, these catalogs are HUGE. 70GB? 25GB? That's 10 to 30 times the
>size of the entire cygwin distribution, source and all -- for one
>catalog. Our mirrors probably won't accept that.
I've been trying not to offer an opinion here but it isn't clear to me
why so many people voted +1 for this package. It seems like we're
adding a huge package to the distribution just to help out a very
miniscule user base. Do we really need this package in the Cygwin
distribution?
cgf
next prev parent reply other threads:[~2011-11-07 16:18 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
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 [this message]
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=20111107161723.GB4738@trixie.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).