Re: environment variables for ghc
Frederik Eaton <frederik <at> ugcs.caltech.edu>
2005-03-09 19:55:11 GMT
On Wed, Mar 09, 2005 at 08:14:24PM +0100, Tomasz Zielonka wrote:
> On Wed, Mar 09, 2005 at 10:27:28AM -0800, Frederik Eaton wrote:
> > On Wed, Mar 09, 2005 at 07:03:38PM +0100, Tomasz Zielonka wrote:
> > >
> > > I was complaing (only to myself) that rsync doesn't allow to put some
> > > common options in ~/.rsyncrc or an environment variable. Then I simply
> > > added an alias in my .bash_profile:
> > >
> > > alias rsync='rsync -v --progress'
> > >
> > > Unfortunately, this is still something that developers would like to
> > > know when facing a bug report :)
> > Right. Well, to get it to work from makefiles etc., I'd need to create
> > a script in my path, something like
> > #!/bin/sh
> > ghc -i$HSPATH -package-conf $HSPKGCONF "$ <at> "
> > And I'd call it ghc. The thing is, I'm arguing that enough people
> > would do this that we should standardize on the environment variable
> > names. Plus, yeah, as you point out, I could just as well forget to
> > mention in a bug report that 'ghc' is my own special script.
> Why not simply do:
> /usr/.../ghc $GHCOPTS "$ <at> "