public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: gcc-core requires libvtv0?
Date: Tue, 13 Oct 2015 16:11:00 -0000	[thread overview]
Message-ID: <87d1wiychk.fsf@Rainer.invalid> (raw)
In-Reply-To: <561D21F7.3020403@cornell.edu> (Ken Brown's message of "Tue, 13	Oct 2015 11:23:35 -0400")

Ken Brown writes:
> Yes, that's what I meant---manually install the test version.  It's
> completely harmless to do that, since the library isn't used by the
> current version of any other package.

But someone installing the current gcc will not get the correct
libraries installed unless these get pulled in by other packages (I
believe they are, but I haven't checked), so that's still wrong.  If a
test package has different dependencies than the current one, setup.hint
should have the dependencies for "curr" correct and anyone installing
"test" needs to be aware that there's maybe some dependencies to install
by hand, which the announcement should helpfully provide.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

--
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

  reply	other threads:[~2015-10-13 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  9:39 Andrew Schulman
2015-10-13 10:45 ` Achim Gratz
2015-10-13 11:57   ` Ken Brown
2015-10-13 13:31     ` Achim Gratz
2015-10-13 15:23       ` Ken Brown
2015-10-13 16:11         ` Achim Gratz [this message]
2015-10-13 14:57   ` cyg Simple
2015-10-13 16:09     ` Achim Gratz
2015-10-13 16:42       ` Marco Atzeri
2015-10-14 11:14 ` Andrew Schulman

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=87d1wiychk.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).