X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_CG X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: paul Subject: Re: Creating CD of installation packages: Download incomplete. Try again? Date: Mon, 26 Nov 2012 02:25:06 +0000 (UTC) Lines: 28 Message-ID: References: <0105D5C1E0353146B1B222348B0411A20AD854C98A AT NIHMLBX02 DOT nih DOT gov> <20121125072140 DOT GB12513 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor cygwin.com> writes: > > On Sat, Nov 24, 2012 at 07:31:48PM +0000, Paul wrote: > >Robert Pendell writes: > >>It isn't obsolete. All obsolete packages get assigned to _obsolete > >>group. _autorebase is assigned to _PostInstallLast and is still an > >>active group. It is likely hidden by default to minimize confusion. > > > >I searched http://cygwin.com/setup.html and http://cygwin.com/packages > >for mention of package "groups", _obsolete, and _PostInstallLast. > >Couldn't anything. Are such details available to noncontributors? Can > >I also assume that "_update-info-dir 01088-1" is not obsolete? > > Unsurprisingly, and as correctly asserted above, you can assume that a > package is only obsolete when it is specifically marked as obsolete. > > There are some categories and packages which are used internally by > setup.exe. If you truly want to understand what they do then inspect > their contents and read the setup source. From the context, I believe that groups like _obsolete and _PostInstallLast are some of these internally used categories. I am not able to dig deeper into their use at the moment. I was just wondering how best to use this information about those groups provided to me to resolve my question. However, I found that simply doing a package search seems to be a good way to determine whether a package is obsolete. It's nice to know that I can delve into the setup source if I wanted to go deeper. Thanks. -- 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