X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Message-ID: <50363E62.1020102@bonhard.uklinux.net> Date: Thu, 23 Aug 2012 15:29:54 +0100 From: Fergus User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10 MIME-Version: 1.0 To: Cygwin ML CC: Fergus Subject: Glitch-free texlive-collection-basic.sh and other uses of setup v.2.510.2.2 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 On today's update of texlive-collection-basic I got the exit message Package: texlive-collection-basic texlive-collection-basic.sh exit code 148 which typically seems to follow most texlive installations. At subsequent uses of setup, even when there is nothing new to install, the "unknown package" /etc/postinstall/texlive-collection-basic.sh is again run, resulting in the same exit code, and this behaviour is recurrent. The attempt takes an unbelievable 4 minutes each time, even on a moderately new and fast machine (XP Pro SP3). There is a way round this. I use good old setup v.2.510.2.2 (c. 2005) having deleted "message:" entries from setup.ini , which this old version doesn't understand. Hey presto, the script is run, exits just fine, and there is no recurrence. There may be other ways, but I don't know them and can't remember reading about them here. With the editing of setup.ini described above which is a bit of a chore, my preference is to use v.2.510 for everything, including brand new installs both of 1.7 and the Legacy 1.5. Doing this, I have not experienced another setup annoyance, where a request to install Cygwin at location H:\ is ignored, and the installation proceeds remorselessly to C:\cygwin\. Unfortunately, despite a clear chain of .. requires: -> requires: -> requires: .. in setup.ini, I found after using v.2.510.2.2 for a brand new install, one missing dependency. I'm not exactly certain how an engine that works its way correctly through very many essentially identical instruction lists can have slipped up with just one, but this did occur [can't remember details but they are there somewhere on this list and I will look for them]. This rather dented my confidence in and reliance upon this old favourite. Otherwise I would use it the whole time. Fergus -- 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