Re: Cut down xfree server for XDMCP only

2002-06-15 Thread Larry Hall (RFK Partners, Inc)

At 11:01 AM 6/15/2002, Rasjid Wilcox wrote:
On Sun, 16 Jun 2002 12:30 am, Rasjid Wilcox wrote:
 For example, MySQL use the cygwin dll for their windows
 port (see http://www.mysql.com/downloads/mysql-3.23.html) but they are
 using cygwin 1.3.9 not the current version.  This could cause problems in
 the future if someone does not keep their mysql setup up to date but also
 uses Cygwin and does keep it up to date (or vice-versa).


Actually, I just checked a bit more carefully.  They host the source for 
cygwin 1.3.9, but it looks to me like the actual dll they use is B19 (or at 
least, it is named cygwinb19.dll - perhaps they have a more recent one and 
just name it that for compatibility??).


It's possible.  cygwin1.dll is binary compatible with B19 so they might 
just slip in a more current Cygwin DLL by renaming cygwin1.dll to
cygwinb19.dll.  This avoids a recompile and uses the new DLL.  There are 
other ways around this (like editing the binary and replacing all 
occurrences of cygwinb19.dll with cygwin1.dll   - spacing is important!)
But a simple recompile and relink is the best course of action.  With B19 
so far in the past, it makes no sense to force these contortions/problems
on users, assuming they are still using the B19 DLL in name at least.  You'd 
do well to ask them about this.


Someone please tell me I'm wrong, but won't this potentially cause serious 
problems if someone is running mysql (assuming it really is using B19) and 
also tries to run an up-to-date cygwin install?


You're not wrong.


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




Re: Best place for WindowMaker, Openbox, etc.?

2002-04-29 Thread Larry Hall (RFK Partners, Inc)

At 05:08 PM 4/29/2002, Harold Hunt wrote:
I've created Cygwin setup.exe packages for the X11 window managers
WindowMaker and Openbox.  I have tentatively put them in
release/XFree86/WindowMaker and release/XFree86/openbox... is that a good
idea?  Or, should I give each X package a toplevel directory in release/?


The latter please.

Thanks,



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




Re: xfree packages

2002-04-10 Thread Larry Hall (RFK Partners, Inc)

At 08:29 PM 4/10/2002, Christopher Faylor wrote:
On Wed, Apr 10, 2002 at 09:47:31AM +0200, Jan Nieuwenhuizen wrote:
 Robert Collins [EMAIL PROTECTED] writes:
 
  Setup is case insensitive to package names. I don't see any technical
  issue either way.
 
 Me neither, I only see a social issue: it's just plain irritating for
 people?
 
tar xjf releases/mysTABTAB beep ^U
tar xjf releases/MyTABTAB beep ^U
 
 etc, aargh?  It's ever more annoying when you're using wget, and try
 to guess the name.

I thought I'd replied to this but I guess I hadn't.

I really don't think we should use tab completion as a justification for
picking package names.  The package names should reflect what the
authors want to call the package.  If the name of the package is XFree86,
it should be called XFree86.  Ditto, TeX, or any other package.

AFAICT, both Red Hat and Debian allow upper/lower case, so there's no
reason for us to restrict things.


I went so far as to type a response and then trash it, since I thought it
was getting off-topic for this list.  But thinking again, it supports 
Chris's position, even though it has been mentioned many a time
on the Cygwin list.  I'm thinking of the 'completion-ignore-case' option
in bash.  Seems to me that this addresses the concern.  

I'm certainly all for mixed-case names.





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