public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Robert Collins <robert.collins@itdomain.com.au>
Cc: cygwin@cygwin.com, cygwin-apps@sources.redhat.com
Subject: Re: setup current problems
Date: Thu, 29 Nov 2001 01:19:00 -0000	[thread overview]
Message-ID: <3C05FD7E.2090708@ece.gatech.edu> (raw)
Message-ID: <20011129011900.n0zsKlp3iDuBEwbO6JJppxoFWBrIKACywet0jPhlhWA@z> (raw)
In-Reply-To: <00af01c178b5$aa39e860$0200a8c0@lifelesswks>

Robert Collins wrote:

> 
> Yes, which is why I'm fixing setup, not hammering on your door about
> setup.ini :}.

Okay, well while you're mucking with the setup code, I've got a question 
for you:

1) joe user has the autoconf package installed on his system.  in the 
past, autoconf depended only on cygwin, perl, m4

2) now, the new version of autoconf depends on cygwin, perl, m4, AND 
autoconf-devel + autoconf-stable.  (I KNOW that joe user doesn't have 
autoconf-devel/stable installed because they are brand new packages)

Q: will setup automatically select autoconf-devel and autoconf-stable if 
joe chooses to update his autoconf to the new version?  Why?  (merely 
because -stable and -devel are NEW, or because of the new dependency 
specified by setup.ini for autoconf itself?)

Q: what if the new dependency was on a package -- say, 'squid' -- that 
has been around a long time, and joe has previously skipped (so now it's 
"permanently" skipped).  Will setup present 'squid' as a new required 
dependency and automatically select it if joe decides to update his 
existing autoconf?

--Chuck


--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-11-29  1:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 13:28 Robert Collins
2001-11-19 13:35 ` Charles Wilson
2001-11-19 13:36   ` Robert Collins
2001-11-19 13:48     ` Charles Wilson [this message]
2001-11-19 14:17       ` Robert Collins
2001-11-19 14:47         ` Charles Wilson
2001-11-19 15:00           ` Robert Collins
2001-11-29  2:00             ` Robert Collins
2001-11-29  1:38           ` Charles Wilson
2001-11-29  1:20         ` Robert Collins
2001-11-29  1:19       ` Charles Wilson
2001-11-29  1:11     ` Robert Collins
2001-11-29  1:08   ` Charles Wilson
2001-11-29  1:00 ` Robert Collins

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=3C05FD7E.2090708@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin-apps@sources.redhat.com \
    --cc=cygwin@cygwin.com \
    --cc=robert.collins@itdomain.com.au \
    /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).