RE: New setup uploaded - 2.218.2.8
From: Robert Collins [EMAIL PROTECTED] Date: Fri, 17 May 2002 08:04:42 +1000 -Original Message- From: D G [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 5:32 AM OK. For those of us who did it the wrong way (mine is set to H:\), how can I change the local package directory and still keep all the current package information? Is it automatic? Just change it in setup next time you run it. If you want to keep all the cached data, just copy the directories that look like ftp%3f and their contents to whereever your new local package dir will be. BTW: the default is the dir you run setup from, so you must have created c:\cygwin, copied setup there, and then run it...right? Well, it appears to be automatic since I moved the latest/ contrib/ and http[etc]mirrors.rcn.net[more etc]/ to a seperate drive (not in the path) and setup still ran correctly. I can only conclude that the information about installed packages is stored somewhere else, and that the latest/ contrib/ and [that other directory] are only used to store downloaded packages. On the other hand, would it be a good idea for setup.exe to tag its directories in some way, like with a zero-byte file, so that it doesn't take just any old setup.ini file it finds? Mmmm. I'll think about this. I don't want to interfere with users using mirroring tools. Rob -- Daniel [EMAIL PROTECTED] (remove the Z-'s to reply--they're what I do when I read spam) -- ___ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: New setup uploaded - 2.218.2.8
-Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 7:05 PM -Original Message- From: Harig, Mark A. [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:42 AM Should this behavior of setup.exe's searching the directory tree below the '/' mount point be documented, or should it be changed? Setup would only look under '/' if you chose the dos location of '/' as your 'local package directory. If it's not clear that doing that is a 'bad thing', then we need to change that screen to make it obvious. Cygwin setup wants a directory all to itself to use as it's package cache. Rob I think I see now. I was simply letting 'setup.exe' use its defaults. It defaults to using 'c:\cygwin' for the Root Install Directory and 'c:\cygwin' for the Local Package Directory. I assumed that setup was searching in the '/' directory tree, but that was just a coincidence because my '/' mount point is 'c:\cygwin'. In fact, setup searches in whatever location is provided for Local Package Directory. I changed my Local Package Directory setting to c:\cygwin\setup (a directory that did not exist), and setup created the needed directory. None of the parsing errors that I reported earlier were generated because setup no longer finds invalid 'setup.ini' files from other, non-setup packages. How to make setup.exe more robust? Because setup.exe is not the only program to use the name 'setup.ini' and because the user can change the location of Local Package Directory, my guess is that this problem will keep occuring for users. When setup.exe identifies errors in other packages' setup.ini files, it will be, in effect, pointing to the setting of Local Package Directory, but this isn't evident to the user. Instead of searching the directory tree below whatever is set for Local Package Directory, would it be possible for setup.exe only to look for setup.ini at the top directory for that tree? This would still allow the user to change Local Package Directory, but restrict the file in which the error could occur. The Parsing Errors messages could then locate and identify this file for the user instead of locating errors in other files. -mark -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: New setup uploaded - 2.218.2.8
From: Harig, Mark A. maharig at idirect dot net I think I see now. I was simply letting 'setup.exe' use its defaults. It defaults to using 'c:\cygwin' for the Root Install Directory and 'c:\cygwin' for the Local Package Directory. I assumed that setup was searching in the '/' directory tree, but that was just a coincidence because my '/' mount point is 'c:\cygwin'. In fact, setup searches in whatever location is provided for Local Package Directory. I changed my Local Package Directory setting to c:\cygwin\setup (a directory that did not exist), and setup created the needed directory. None of the parsing errors that I reported earlier were generated because setup no longer finds invalid 'setup.ini' files from other, non-setup packages. OK. For those of us who did it the wrong way (mine is set to H:\), how can I change the local package directory and still keep all the current package information? Is it automatic? What about the latest and contrib directories? Are those obsolete? On the other hand, would it be a good idea for setup.exe to tag its directories in some way, like with a zero-byte file, so that it doesn't take just any old setup.ini file it finds? -- Daniel [EMAIL PROTECTED] (remove the Z-'s to reply--they're what I do when I read spam) -- ___ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: New setup uploaded - 2.218.2.8
At 03:31 PM 5/16/2002, D G wrote: OK. For those of us who did it the wrong way (mine is set to H:\), how can I change the local package directory and still keep all the current package information? Is it automatic? What about the latest and contrib directories? Are those obsolete? Yes, latest and contrib are obsolete. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: New setup uploaded - 2.218.2.8
-Original Message- From: D G [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 5:32 AM OK. For those of us who did it the wrong way (mine is set to H:\), how can I change the local package directory and still keep all the current package information? Is it automatic? Just change it in setup next time you run it. If you want to keep all the cached data, just copy the directories that look like ftp%3f and their contents to whereever your new local package dir will be. BTW: the default is the dir you run setup from, so you must have created c:\cygwin, copied setup there, and then run it...right? On the other hand, would it be a good idea for setup.exe to tag its directories in some way, like with a zero-byte file, so that it doesn't take just any old setup.ini file it finds? Mmmm. I'll think about this. I don't want to interfere with users using mirroring tools. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: New setup uploaded - 2.218.2.8
On Fri, 17 May 2002 03:31:36 +0800 D G [EMAIL PROTECTED] wrote: From: Harig, Mark A. maharig at idirect dot net I think I see now. I was simply letting 'setup.exe' use its defaults. It defaults to using 'c:\cygwin' for the Root Install Directory and 'c:\cygwin' for the Local Package Directory. I assumed that setup was searching in the '/' directory tree, but that was just a coincidence because my '/' mount point is 'c:\cygwin'. In fact, setup searches in whatever location is provided for Local Package Directory. I changed my Local Package Directory setting to c:\cygwin\setup (a directory that did not exist), and setup created the needed directory. None of the parsing errors that I reported earlier were generated because setup no longer finds invalid 'setup.ini' files from other, non-setup packages. OK. For those of us who did it the wrong way (mine is set to H:\), how can I change the local package directory and still keep all the current package information? Is it automatic? What about the latest and contrib directories? Are those obsolete? On the other hand, would it be a good idea for setup.exe to tag its directories in some way, like with a zero-byte file, so that it doesn't take just any old setup.ini file it finds? 1. Create a new directory like c:\zip\Cygwin\ to be the local directory. 2. Move all applicable files and directories to that directory. Examples: setup.exe, setup.ini, release\, contrib\, latest\, ftp%3a*\ Directories contrib\ and latest\ are obsolescent, but may still have useful files under them. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Re: New setup uploaded - 2.218.2.8
-Original Message- From: Michael A Chase [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 8:11 AM Directories contrib\ and latest\ are obsolescent, but may still have useful files under them. If you want to leverage those files, move the contrib/* ands latest/* directories to release/*. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: New setup uploaded - 2.218.2.8
On Fri, May 17, 2002 at 08:04:42AM +1000, Robert Collins wrote: On the other hand, would it be a good idea for setup.exe to tag its directories in some way, like with a zero-byte file, so that it doesn't take just any old setup.ini file it finds? Mmmm. I'll think about this. I don't want to interfere with users using mirroring tools. I think this is really not a great idea. The local directory that setup.exe uses is supposed to be only for that purpose. Adding zero length files for people who don't get the concept seems like the wrong way to go. Especially since I can easily see the setup.exe is creating zero length files!!! How I stop this comments here. There really has to be a limit on how much we coddle people who make bad decisions, IMO. On the other hand, having setup.exe complain when someone specifies an existing populated directory that has no setup.ini files in it, might not be a bad idea. I think that something like this would be a great idea for some intrepid setup.exe patcher. Another plan would be not to parse any setup.ini file that was missing both of the setup-*: options. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: New setup uploaded - 2.218.2.8
On Fri, 17 May 2002 08:21:06 +1000 Robert Collins [EMAIL PROTECTED] wrote: -Original Message- From: Michael A Chase [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 8:11 AM Directories contrib\ and latest\ are obsolescent, but may still have useful files under them. If you want to leverage those files, move the contrib/* ands latest/* directories to release/*. Does that mean setup.exe is going to stop finding files under those directories? Last time I checked it was able to. I thought that if the local directory already contained contrib/ and latest/, we didn't want the files to have to be moved or re-downloaded. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Re: New setup uploaded - 2.218.2.8
-Original Message- From: Michael A Chase [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 11:41 AM If you want to leverage those files, move the contrib/* ands latest/* directories to release/*. Does that mean setup.exe is going to stop finding files under those directories? Last time I checked it was able to. I thought that if the local directory already contained contrib/ and latest/, we didn't want the files to have to be moved or re-downloaded. Recall my comment the move to the release directory will cause folk to download things again. Oh well, nevermind. The reason that contrib and latest will be ignored is that setup.ini no longer refers to them. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: New setup uploaded - 2.218.2.8
Should this behavior of setup.exe's searching the directory tree below the '/' mount point be documented, or should it be changed? Changed, please - or at least setup should run some sort of sanity check on the files it finds before trying to parse them. I got caught with something similar recently - I had renamed an old setup.ini at the top level of my local dir to setup.ini.sav (so I could later diff with the new one), but when installing setup used the setup.ini.sav file instead of the setup.ini it had downloaded to the mirror subdirectory. -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: New setup uploaded - 2.218.2.8
-Original Message- From: Harig, Mark A. [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:42 AM Should this behavior of setup.exe's searching the directory tree below the '/' mount point be documented, or should it be changed? Setup would only look under '/' if you chose the dos location of '/' as your 'local package directory. If it's not clear that doing that is a 'bad thing', then we need to change that screen to make it obvious. Cygwin setup wants a directory all to itself to use as it's package cache. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: New setup uploaded - 2.218.2.8
On Thu, May 16, 2002 at 09:18:05AM +1000, Robert Collins wrote: -Original Message- From: Cliff Hones [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 1:51 AM To: [EMAIL PROTECTED] Subject: Re: New setup uploaded - 2.218.2.8 Should this behavior of setup.exe's searching the directory tree below the '/' mount point be documented, or should it be changed? Changed, please - or at least setup should run some sort of sanity check on the files it finds before trying to parse them. There is a sanity check. It's called parsing the file. If the file is called setup.ini, setup *will* try to parse it. It shouldn't parse non-setup.ini files anymore (thanks Chris). By that Robert means that files named setup.ini.sav will no longer be parsed. Just files who exactly match setup.ini. Or, er, there may still be one bug lurking which causes something like foosetup.ini to be matched in some cases but that should be fixed soon. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
