From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: setup.exe with packages specified downloads multiple versions [?]
Date: Fri, 30 Oct 2015 00:45:00 -0000 [thread overview]
Message-ID: <563281B1.7050708@gmail.com> (raw)
In-Reply-To: <CAL1QdWeuE4x8pzb_2EH4w7Y7=AS3znijO0vegaMkczup+cO8MQ@mail.gmail.com>
On 29/10/2015 20:53, Roger Pack wrote:
> As a note, running this:
>
>
> setup-x86.exe ^
> --quiet-mode ^
> --no-admin ^
> --no-startmenu ^
> --no-shortcuts ^
> --no-desktop ^
> --site http://mirrors.xmission.com/cygwin/ ^
> --root %cd% ^
> --packages ^
> ed,curl,wget,subversion,texinfo,gcc-g++,bison,flex,cvs,yasm,automake,libtool,autoconf,gcc-core,cmake,git,make,pkg-config,zlib1g-dev,mercurial,unzip,pax,ncurses,patch
>
> downloads seemingly lots of versions of particular packages [?] (note
> the duplicates of autoconf and automake, various versions:
>
[cut]
>
> Not sure if that's expected or not.
> Cheers!
> -roger-
Setup is correct.
Autoconf and automake are wrapper managing
alternative version of the same package.
If you looks on setup.ini content:
@ autoconf
sdesc: "Wrapper scripts for autoconf commands"
ldesc: "Wrapper scripts for autoconf commands"
category: Devel
requires: bash sed autoconf2.1 autoconf2.5 cygwin
....
@ automake
sdesc: "Wrapper scripts for automake and aclocal"
ldesc: "Wrapper scripts for automake and aclocal"
category: Devel
requires: bash gawk automake1.4 automake1.5 automake1.6 automake1.7
automake1.8 automake1.9 automake1.10 automake1.11 automake1.12
automake1.13 automake1.14 automake1.15 cygwin
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-10-29 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 0:40 Roger Pack
2015-10-30 0:45 ` Marco Atzeri [this message]
2015-10-30 8:05 ` Roger Pack
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=563281B1.7050708@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).