From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Downgrading Cygwin components and dependencies
Date: Fri, 8 May 2020 17:28:53 +0200 [thread overview]
Message-ID: <690d1a13-6993-2890-add1-4f7dab8db3d4@gmail.com> (raw)
In-Reply-To: <CAHvU03VDNSeQkFLwMXY9o_=nYSLi9ViUUzXLwA157rr-77Dt8Q@mail.gmail.com>
Am 08.05.2020 um 14:10 schrieb Maarten Hoes via Cygwin:
> Hi,
>
>
> In another thread (that I did not want to hijack) it was mentioned that you
> can downgrade (parts of) your cygwin installation by selecting
> previous/older versions of things.
>
> In the cygwin installer, I can select (a few) older versions of the
> components by clicking on the drop down menu next to the package names.
> However, it appears that this only downgrades the package you explicitly
> selected, and does not automatically downgrade components that depend on
> it.
Correct. It is supposed to be used on the seldom case that a specific
new package is not working
> For example, if I select a previous version of 'xorg-server', I would
> expect that all packages that have a dependency on that to also be
> downgraded (in this example, perhaps 'xorg-server-common' and
> 'xorg-server-extra'). But this does not seem to be the case.
To much expectation. It is not the case.
The list of packages built with the same source is mentioned here:
https://cygwin.com/packages/summary/xorg-server-src.html
Setup is NOT looking at this information.
> Is there a way
> to automatically do this (for X11, in my use case) ? Or do you have to
> figure out the dependencies yourself ? Am I simply doing something wrong
> here ?
Manual process.
>
> Any and all help is appreciated,
>
Why do you need to downgrade the X server ?
Regards
Marco
next prev parent reply other threads:[~2020-05-08 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 12:10 Maarten Hoes
2020-05-08 15:28 ` Marco Atzeri [this message]
2020-05-08 16:44 ` Maarten Hoes
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=690d1a13-6993-2890-add1-4f7dab8db3d4@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).