--- Richard Frith-Macdonald <[EMAIL PROTECTED]> wrote: > > On 4 Feb 2005, at 18:37, Gregory John Casamento wrote: > > > All but #1. I'm confused, however, first you want avoid installing > > GNUstep > > altogther (by linking with it statically), and then you want to install > > GNUstep, even if the user currently has GNUstep, but you don't want to > > interfere with thier installation of it. > > > > Wouldn't it be easier to simply tell the user that your program > > requires > > GNUstep and point them to the appropriate directions for installing it > > on their > > system? > > This is quite reasonable when selling a package to a dumb corporate. > They just want to be able to run a simple package installation (perhaps > just > un-tarring an image) and then type a simple command to run the > application. > > You can do that quite easily by giving them a simple shell script which > sets > up the environment to use the correct installation of GNUstep ... then > you don't > care if they have an older installation lying around on the machine, > and you > don't care if someone else has installed another version of GNUstep > anywhere.
Of course this is possible, my question centered more around the "Why" than the "How". GJC ===== Gregory John Casamento -- CEO/President Open Logic Corp. (A MD Corp.) ## Maintainer of Gorm (IB Equiv.) for GNUstep. _______________________________________________ Help-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gnustep
