[17467] in Athena Bugs

home help back first fref pref prev next nref lref last post

Re: mkmailcaps script

daemon@ATHENA.MIT.EDU (t. belton)
Mon Jan 10 12:24:37 2000

Date: Mon, 10 Jan 2000 12:24:29 -0500 (EST)
From: "t. belton" <tbelton@MIT.EDU>
To: Jacob Morzinski <jmorzins@mit.edu>
cc: bug-infoagents@mit.edu
In-Reply-To: <Pine.GSO.4.21.0001090456520.10454-100000@x15-cruise-basselope.mit.edu>
Message-ID: <Pine.GSO.3.96L.1000110121938.12019A-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 9 Jan 2000, Jacob Morzinski wrote:
> While I was looking around I noticed that the script
>  /mit/infoagents/share/Netscape/mkmailcaps
> has a small bug.  Line 32 incorrectly sets $oldbindir of sgi
> platforms to "sgibin", when in fact the sgi's are new enough
> that they've always used "arch/@sys/bin".

Thanks - I'll take a look at that, although I'm pretty sure it doesn't
make a difference to the final file which gets generated (I don't have it
in front of me right this second.)

> (If it matters, I'm leaning towards rolling my own mailcap files,
> because I'd like to make a file that doesn't have to make
> assumptions about what lockers are attached.)

Well, the Athena scripts can assume that certain lockers are attached for
Netscape purposes, because of the Netscape wrapper scripts, but that
certainly doesn't help if you're using mailcap for other things. I'm
curious, though - how would you go about making a mailcap that *doesn't*
assume a certain number of pre-attached paths? The format doesn't really
have the ability to do anything clever ... and I'm not sure that using
fully qualified AFS paths (rather than /mit/lockername/ paths) is a good
idea. 

-Todd



home help back first fref pref prev next nref lref last post