Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: Re: RPM installer (was Re: SETUP WIZARD FOR CYGWIN?XFREE86) From: Robert Collins To: Dario Alcocer Cc: Charles Wilson , cygwin AT cygwin DOT com In-Reply-To: <15200.14597.953781.596499@coyote.priv.helixdigital.com> References: <17B78BDF120BD411B70100500422FC6309E2FD AT IIS000> <15199 DOT 13618 DOT 671411 DOT 755243 AT coyote DOT priv DOT helixdigital DOT com> <996103548 DOT 18053 DOT 7 DOT camel AT lifelesswks> <3B5F5731 DOT 1090000 AT ece DOT gatech DOT edu> <15200 DOT 14597 DOT 953781 DOT 596499 AT coyote DOT priv DOT helixdigital DOT com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 27 Jul 2001 09:52:28 +1000 Message-Id: <996191548.22846.16.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 26 Jul 2001 23:38:44.0235 (UTC) FILETIME=[1BB5B5B0:01C1162C] On 26 Jul 2001 08:36:37 -0700, Dario Alcocer wrote: > >>>>> "Chuck" == Charles Wilson writes: > > Chuck> **IF** you're going to pursue this, The Right Way(tm) is to > Chuck> build a special cygwin1.dll AND import lib environment, > Chuck> where the "shared memory region name" is different -- and > Chuck> perhaps the dll name itself, as well. Also, it should use > Chuck> a different registry key for mounts and such, > Chuck> probably. (Check the cygwin archives wrt. error_start and > Chuck> gdb for some info on how to do the "shared memory region > Chuck> name" thing). Then, build your special ash and rpm and db > Chuck> and utils within that environment (you may need to also > Chuck> build gcc?) Mounts shouldn't be changed - it needs to install into the cygwin mounted directories. > Chuck> The difficulty here is you've got to maintain TWO separate > Chuck> binaries for your core utilities -- one set of (cygwin > Chuck> itself, ash, rpm, db, etc) for the "real" system and one > Chuck> set for the "mini" environment. The mini environment shouldn't need different binaries, just a copy in the toolkit, launched with a custom PATH. > I think this would be the major sticking point; having a parallel > set of Cygwin binaries would be problematic, both for maintenance and > support. I don't think changing the .dll name would be needed - it would be outof the system path, and in the same dir as all the binaries for the toolkit. Changing the shared memory area is needed IMO, but that can be done by a simple #ifdef in one location in the cygwin dll source. ie #if _CYGWIN_INSTALLER_DLL_ #else #endif 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/