From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gcc-core requires libvtv0?
Date: Tue, 13 Oct 2015 16:42:00 -0000 [thread overview]
Message-ID: <561D3463.7030803@gmail.com> (raw)
In-Reply-To: <87h9luycmm.fsf@Rainer.invalid>
On 13/10/2015 18:08, Achim Gratz wrote:
> cyg Simple writes:
>> On 10/13/2015 6:44 AM, Achim Gratz wrote:
>>> I guess we need to
>>> enable different dependencies for "prev", "curr" and "test" in setup.ini.
>>>
>>
>> I'm surprised that this hasn't occurred already because of this. Yes
>> the dependency tree needs to be needs to be cognizant of version of
>> dependencies as well as differing libraries.
Already happened all the time we have test versions that bump libs.
It is also one of the reason why going "prev" is not always possible.
> It likely would have occured already if it was a simple patch to setup.
> But it minimally needs changes to cygport, setup.hint, setup.ini and
> upset as well, so here we are.
I agree. It is a really a substantial job and should include
moving from setup.hint to <package>-<version>.hint to correctly manage
all dependencies.
As upset seems a big blob, I doubt we will have voluntaries to add that
portion. Plus of course we need to modify setup-<arch>.exe to correctly
manage the new setup.hint.
> Regards,
> Achim.
>
Regards
Marco
--
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-13 16:42 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
2015-10-13 14:57 ` cyg Simple
2015-10-13 16:09 ` Achim Gratz
2015-10-13 16:42 ` Marco Atzeri [this message]
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=561D3463.7030803@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).