Subject: RE: MC can't find libgpm.so.1

From: Fernando <[email-masked]>
Date: Sun, 21 Jul 1996 11:17:42 -0400 (EDT)

I will release a new "mc" package next week. It is possible to
select whether to include gpm support or not, but only at compile time.
I have two options:

	1) Include two binaries: mc (with gpm support) and mc-nogpm
		I could ask the user which one to install
	
	2) Make gpm a requirement, not only a suggestion

Which option would you prefer? Do you have a better suggestion?

Cheers,
	Fernando Alegre
	[email-masked]

---

From: Dale Scheetz <[email-masked]>
Date: Sun, 21 Jul 1996 12:54:08 -0400 (EDT)

> Which option would you prefer? Do you have a better suggestion?
If the gpm library isn't too large you could link it static (as opposed to
making it shared) at build time. Unless mc does something special to
determin mouse availability, it should run fine and work with a mouse if
gpm is running, and have no mouse behavior if it isn't. Seems to me that
it used to be built like this in the ancient past.

Luck,

Dwarf

------------                                          --------------

aka   Dale Scheetz                   Phone:   1 (904) 877-0257
      Flexible Software              Fax:     NONE 
      Black Creek Critters           e-mail:  [email-masked]

------------ If you don't see what you want, just ask --------------

---

From: Alexander Goldstein <[email-masked]>
Date: Mon, 22 Jul 1996 11:22:16 -0500 (CDT)

> Which option would you prefer? Do you have a better suggestion?

What about splitting gpm into gpm-bin, gpm-lib, and gpm-dev and having mc
depend on gpm-lib.  This would seems more consistent with the rest of the
system (maybe gpm-lib and gpm-dev could be combined).