From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Apparent bug in either (1) Cygwin default Package-list or (2) Package "bzr" dependency-list
Date: Wed, 24 Jun 2020 22:34:14 +0100 [thread overview]
Message-ID: <f0443281-c1bc-f4ae-8a3a-1f56496276ab@dronecode.org.uk> (raw)
In-Reply-To: <d25f12af-f495-fa79-c29f-aa8f0cb179d7@SystematicSw.ab.ca>
On 21/06/2020 17:15, Brian Inglis wrote:
> On 2020-06-20 08:41, Jon Turney wrote:
>> On 19/06/2020 07:55, Brian Inglis wrote:
>> This analysis is not complete or correct because it doesn't take 'obsoletes:'
>> into account:
>> https://sourceware.org/git/?p=cygwin-apps/calm.git;a=commitdiff;h=d75abceedb46749982669236c5c102796a1fbfb1;hp=f92ad1d5c292ed54e7a62f5c52280efab8267f37
>> It does seem that things aren't working as intended, though.
>
> So does that obsoletes: mean something different than category: _obsoletes,
> which I view as a (Debian-like) virtual package declaration?
There's no need to guess, when the source code is available to inspect.
All the '_obsolete' category (note no 's') does is cause packages to get
hidden by the 'Hide obsolete packages' filter in setup (which is on by
default).
So yes, these are completely different things.
> Are obsoletes and pre-depends documented anywhere else (and any other new
> keywords)?
https://cygwin.com/packaging-hint-files.html
https://sourceware.org/cygwin-apps/setup.ini.html
next prev parent reply other threads:[~2020-06-24 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 3:33 My Name
2020-06-19 6:55 ` Brian Inglis
2020-06-19 9:39 ` marco atzeri
2020-06-20 14:41 ` Jon Turney
2020-06-20 14:44 ` Marco Atzeri
2020-06-21 16:15 ` Brian Inglis
2020-06-21 18:04 ` My Name
2020-06-22 2:21 ` Allen Hewes
2020-06-22 2:45 ` My Name
[not found] ` <MN2PR17MB39993A62062F020FE99CA0B6B8970@MN2PR17MB3999.namprd17.prod.outlook.com>
[not found] ` <CAGUd5DW8vwBB3QtOLaTB1FhPVGB9ugx+xxo=CxCWFVB3hWFsMw@mail.gmail.com>
2020-06-22 5:26 ` Allen Hewes
2020-06-22 5:20 ` Marco Atzeri
2020-06-22 5:49 ` Allen Hewes
[not found] ` <CAGUd5DXo=Wu1jx64OkQbjHtvC_5gcaUJF6_mnL0YH=Xmhd_x6g@mail.gmail.com>
2020-06-22 6:54 ` Allen Hewes
2020-06-22 7:02 ` Allen Hewes
2020-06-24 21:34 ` Jon Turney [this message]
2020-06-25 11:53 ` Brian Inglis
2020-06-25 21:48 ` Jon Turney
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=f0443281-c1bc-f4ae-8a3a-1f56496276ab@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).