public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] Macaulay2 1.1
Date: Thu, 08 Jan 2009 10:30:00 -0000	[thread overview]
Message-ID: <20090108103011.GA14304@calimero.vinschen.de> (raw)
In-Reply-To: <200901080142.n081gkLF021445@u123.math.uiuc.edu>

On Jan  7 19:42, Daniel R. Grayson wrote:
> You must be reading her message differently from the way I did.

Yaakov got the message basically right.  I used the gc package as an
unfortunate example but this doesn't invalidate the fact that it would
be much more feasible to have the extra libs your package depends upon
as distinct Cygwin packages.  I explained why, and you would certainly
not be the first one who would pack extra packages which your main
package depends upon.

> In any case, if it were to turn out that Macaulay 2 were interesting to cygwin,
> but one of the libraries Macaulay 2 depends on was not interesting to cygwin,
> then I wouldn't have to package that library, would I?  I could just include
> the source for it in the Macaulay 2 package.  Otherwise it's a catch-22.
> 
> So I think the question of whether ITP's for the dependent packages would
> succeed on their own merits is moot.

Not really.  Here's the list of packages you talked about:

  gc               - already available.
  ntl              - Packed in Fedora, Cygwin package only needs GTG.
  singular-factory - Didn't find that one, but...
  singular-libfac  - Is packed in Fedora, only GTG needed.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  reply	other threads:[~2009-01-08 10:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 19:04 Daniel R. Grayson
2009-01-07 19:14 ` Christopher Faylor
2009-01-07 19:17   ` Christopher Faylor
2009-01-07 19:39   ` Daniel R. Grayson
2009-01-07 22:56 ` Yaakov (Cygwin/X)
2009-01-08  1:42   ` Daniel R. Grayson
2009-01-08 10:30     ` Corinna Vinschen [this message]
2009-01-08 16:47       ` Daniel R. Grayson
2009-01-08 18:13         ` Yaakov (Cygwin/X)
  -- strict thread matches above, loose matches on Subject: below --
2008-11-12  1:53 Daniel R. Grayson
2008-11-13 14:24 ` Daniel R. Grayson
2008-11-13 14:33   ` Corinna Vinschen
2008-11-13 18:17     ` Daniel R. Grayson
2008-11-14  8:52       ` Corinna Vinschen
2008-11-14  9:01         ` Yaakov (Cygwin Ports)
2008-11-14  9:24           ` Corinna Vinschen
2008-11-14 14:18           ` Daniel R. Grayson
2008-11-14 15:13     ` Reini Urban
2008-11-17 19:42 ` Dr. Volker Zell

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=20090108103011.GA14304@calimero.vinschen.de \
    --to=corinna-cygwin@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).