X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Sat, 6 Dec 2008 12:42:36 +0100 From: ColdShine To: cygwin@cygwin.com Subject: Re: Setup.exe: all files in one common directory? (not per-server) In-Reply-To: <02ea01c9575d$9f6e49b0$3201a8c0@aew2knew> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <01b401c95743$52f4a580$3201a8c0@aew2knew> <4939DFD9.57A0178B@dessent.net> <01f201c9574b$900043f0$3201a8c0@aew2knew> <4939E651.BFEF677C@dessent.net> <02ea01c9575d$9f6e49b0$3201a8c0@aew2knew> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 2008/12/6 sowiso : > > F:\CygwinInstall\release. That would be the sh*t.. And *all* packages > going in there. And one setup.ini. That's the best solution IMHO. Use NTFS junctions. Once you see you have to use a different server, quit setup, go to the newly created Release dir, clear it (or, if it wasn't created, create it anew), use linkd (MS WRK) or junction (Wininternals, now MS) to link it to F:\CygwinInstall\Release, and you're done. This will merge every Release dir, with all possible further consequencies you can't predict. But you'll have your _single_ release directory. I'm not gonna tell you how to have a single setup.ini, though (I'm not even sure whether it'd work). That wouldn't really be a good idea, for the reasons others have exposed here. -- CS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/