Re: [racket-dev] Package cleanup

2017-07-12 Thread Matthew Flatt
At Wed, 12 Jul 2017 17:25:58 -0400, Leif Andersen wrote: > It looks like this is what the docs have to say wrt making tests pass: > ``` > Distribute Native Libraries > > Another option is to build a 64-bit Linux version of the library, > distribute it as a package, and make the package a platform-

Re: [racket-dev] Package cleanup

2017-07-12 Thread Leif Andersen
It looks like this is what the docs have to say wrt making tests pass: ``` Distribute Native Libraries Another option is to build a 64-bit Linux version of the library, distribute it as a package, and make the package a platform-specific dependency of your package for the "x86_64-linux-natipkg" pl

Re: [racket-dev] Package cleanup

2017-07-12 Thread Matthew Flatt
At 12 Jul 2017 16:43:48 -0400, "'John Clements' via Racket Developers" wrote: > I have a bunch of packages that fail because they depend on external > libraries, viz: GLPK, which depends on the glpk library. It’s listed > as having failing tests, because (not surprisingly) it won’t run > without th

Re: [racket-dev] Package cleanup

2017-07-12 Thread 'John Clements' via Racket Developers
> On Jul 12, 2017, at 17:50, Jay McCarthy wrote: > > Yup, we may do that eventually, but we won't start spamming without > permission. I have a bunch of packages that fail because they depend on external libraries, viz: GLPK, which depends on the glpk library. It’s listed as having failing t

Re: [racket-dev] Package cleanup

2017-07-12 Thread Jay McCarthy
Yup, we may do that eventually, but we won't start spamming without permission. Jay On Wed, Jul 12, 2017 at 10:40 AM, Neil Van Dyke wrote: > In case anyone is as mentally slow as I am right after lunch: I think this > is the gray button labeled like: "515 todos. Click here to see them." > > Woul

Re: [racket-dev] Package cleanup

2017-07-12 Thread Neil Van Dyke
In case anyone is as mentally slow as I am right after lunch: I think this is the gray button labeled like: "515 todos. Click here to see them." Would it be good to have an automated monthly email to package owners, itemizing the issues with each of their packages? (Each email address would g

[racket-dev] Package cleanup

2017-07-12 Thread Jay McCarthy
If you go to the package site now, then every package table will tell you how many of the packages shown have some sort of flaw. The flaws are: failing to build, tests failing, missing documentation, missing tags, or missing a description. (We need to fix it a little bit because some packages aren'