Hmm, well note that I'm not touching or sourcing any of the ~/.cshrc
files.  The entire shell script that I'm sourcing is here:

[localhost:share/init/tcsh] mat% more init.csh

set path = ( /sw/bin /sw/sbin $path /usr/X11R6/bin )

if ( $?MANPATH) then
  setenv MANPATH /sw/share/man:/sw/man:${MANPATH}:/usr/X11R6/man
  setenv MANPATH

if ( $?DISPLAY) then
  echo "Your X11 server is set to set to display:" $DISPLAY
  setenv DISPLAY localhost:0.0

So its basically only doing three things:
 1. making sure that gimp will be in the path
 2. making sure the man pages will be available
 3. setting display to run on localhost

fink already does these things so if a MacGIMP-installer user installs
the fink, there's a fair amount that's redundant.

Quite frankly, I'm ready to give up on Apple's pkg stuff.  The only thing
it has to offer at this point is a GUI installation method, which, from
reading the mailing lists, it looks like the fink will have at some point
in the not-too-distant future.  (yes, I realize that there is some
disagreement on this point, but there was enough interest that I'm
confident it will occur.  The best part about this is that with a fink
GUI, you could uninstall, and Apple makes this almost completely
impossible since they haven't documented the receipts, among other

Maybe I should be spending my time working on a GUI for fink.  If anyone
is already working on that, can you email me?  I'd like to help out.

I still find that a year after OS X is available, Apple's lack of
leadership in a rational packaging system is astounding.


On Sun, 20 Jan 2002, David R. Morrison wrote:
> Mat Caughron <[EMAIL PROTECTED]> wrote:
> > Hi David:
> >
> > The issue of setting the proper (and non-conflicting!) shell variables is
> > a very important one, and that's why I'd like for packaged
> > installations, particularly ones depending on X11, to stick as close as
> > possible to the default fink install.
> >
> > >In either case, though, there is a fundamental problem of getting the user
> > >to include the correct thing in a .cshrc or .tcshrc file.  How do you
> > >handle that?
> >
> > In the installer I'm now building, there is a csh file that is sourced by
> > adding a second line to   /private/etc/csh.cshrc
> > This way, all users get some helpful default values in their DISPLAY and
> > PATH variables on login.
> >
> You might want to look back in the mailing list archives, I think it was
> the fink-users list in November or December.  There was an extensive
> discussion of the problems some users were having with .cshrc or .tcshrc
> type files being sourced.  One of the difficulties came from installing
> some other software, I think it was CodeWarrior, which had added something
> to one of these files in a manner incompatible with fink's.
> This entire issue needs a lot of thought by all concerned.
> > There are pros and cons to putting everything in a /macgimp directory and
> > that's something I considered.
> > /sw/macgimp makes more sense to me since it would mean less clutter.
> >
> Putting ANYTHING into /sw which is not installed by dpkg/apt-get violates
> the spirit of fink.  Please don't.
> >
> >
> >
> > Mat Caughron
> >
> -- Dave

Fink-devel mailing list

Reply via email to