[racket-dev] Latex files

From: Sam Tobin-Hochstadt (samth at ccs.neu.edu)
Date: Sat Feb 19 09:58:30 EST 2011

On Sat, Feb 19, 2011 at 9:50 AM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> Does it seem okay to provide a script that downloads the .cls file
> from the jfp website and tuck it into the (already installed)
> distribution (presumably in a user-specific place)?

Yes, this is a well-known workaround in these sorts of situations.
It's used for packages that install Flash on lots of Linux
distributions, for example.

I think it would probably be sufficient to provide a .cls file that
errors with a message indicating where to go to get the file, although
the script you describe would certainly be a helpful addition.

> If so, then we can at least set up a drdr test that does that and
> checks to see if scribble produces exactly the same .pdf file for some
> well known scribble input file, so we get notified problems when they
> move the url or make a new version of the file or something.
> Robby
> On Sat, Feb 19, 2011 at 8:46 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
>> On Sat, Feb 19, 2011 at 8:22 AM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
>>> At Fri, 18 Feb 2011 22:44:54 -0500, Sam Tobin-Hochstadt wrote:
>>>> At least for the JFP file, it's pretty clearly a copyright violation
>>>> for us to distribute the file at all -- on the web page or elsewhere.
>>>> We'd have to download it from the CUP site.
>>>> For the ACM file, I emailed the contact email for the style file about
>>>> the license.
>>> Did you e-mail anyone at JFP, yet?
>> I have not, although one of the JFP editors is on this list :)
>>> Looking again, I can imagine reading the "jfp.cls" file Robby's way.
>>> The intent of "use" may be "produce a document", and the overall intent
>>> might permit redistribution of "jfp.cls" to others who are producing
>>> JFP documents.
>> That's certainly possible, but redistributing the file requires the
>> permission of the copyright holder, and the tone of the notice
>> suggests that they aren't very flexible about these things.
>> --
>> sam th
>> samth at ccs.neu.edu

sam th
samth at ccs.neu.edu

Posted on the dev mailing list.