From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
'Oleksandr Gavenko' <gavenkoa@gmail.com>
Subject: RE: What does mean 'obsolete' category?
Date: Sun, 06 Nov 2011 18:38:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A20A39C92BB5@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <87lirujg4q.fsf@gmail.com>
Oleksandr Gavenko sent the following at Saturday, November 05, 2011 7:37 PM
>Search:
> http://cygwin.com/cgi-bin2/package-grep.cgi?grep=xorg-x11-xwin
>
>take:
> xorg-x11-xwin/xorg-x11-xwin-7.4-1 Obsolete package
>
From setup.ini:
> @ xorg-x11-xwin
> sdesc: "Obsolete package"
> ldesc: "Obsolete package"
> category: _obsolete
>
>That mean 'obsolete' for package?
>
>I search for docs in:
> Cygwin Package Contributor's Guide
> Cygwin User's Guide
> http://sourceware.org/cygwin-apps/setup-head.ini.html
>
>but does not found any relevant docs for 'obsolete' keyword.
>
>Do this mean that package deprecated and I need avoid its uses?
>
>Or it is for a long time does not updated and can have known bugs?
>
>I will be glad if docs updated with appropriate texts.
They are how obsolete packages are removed and replaced by their successors.
Lets look at the setup.ini entry for ash.
@ ash
sdesc: "Replaced by dash"
ldesc: "OBSOLETE PKG: replaced by dash"
category: _obsolete
requires: dash cygwin
version: 20040127-5
install: release/ash/ash-20040127-5.tar.bz2 46 c616cffee0f344c37fd4e045a7a87054
source: release/ash/ash-20040127-5-src.tar.bz2 46 c616cffee0f344c37fd4e045a7a87054
[prev]
version: 20040127-4
install: release/ash/ash-20040127-4.tar.bz2 47178 26b04e64b710f4e9592258446920a992
source: release/ash/ash-20040127-4-src.tar.bz2 140516 7fa68e8ed663ac77b484079aab026ed8
Note that both the install and source tarballs are effectively empty - only 46 bytes.
When setup updates, it first removes the previous version, here ash-20040127-4.tar.bz2,
before trying to install the non-existent contents of ash-20040127-5.tar.bz2. The
requires line then tells setup to install dash, the replacement of ash.
I could be wrong about this, but it seems to me that one other thing that "_obsolete"
does is to move the directory of the package in setup.exe's local package cache to be
a subdirectory of .../release/_obsolete/.
So the category _obsolete means "do not install this" and "you cannot use this
because it is not here", which is a bit stronger than "deprecated" and "avoid".
I hope that helps. (I also hope that that was correct. :-) )
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
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
prev parent reply other threads:[~2011-11-06 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 23:37 Oleksandr Gavenko
2011-11-06 18:38 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
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=0105D5C1E0353146B1B222348B0411A20A39C92BB5@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
--cc=gavenkoa@gmail.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).