Ian Johnson | 17 Apr 22:28 2015
Picon

plot build process?

I'm trying to add some different parameters to plot, but its build makes no sense. I forcefully removed all the plot packages that come with the main distribution, then just tried to raco pkg install the cloned repo. Didn't work, since "plot" somehow needs to mean "plot/plot-lib/plot" but still not really, since there's no main.rkt... I'm lost. Help?

-Ian

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to racket-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/f09504b8-b73f-4295-98dc-e16d95fb161e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thomas Lynch | 17 Apr 05:16 2015

making a new package ... making new docs for the same


Here is the setup I am asking questions against, scroll down to see the questions

set up ------------------------------------------------------------------------
I have split my new package into three directories, like those I see in the distribution:

§lambda1:/home/deep> ls -1
...
liquid
liquid-doc
liquid-lib
...

I then copied over and modified the info.rkt file:

§lambda1:/home/deep/liquid> ls
info.rkt  LICENSE.txt

§lambda1:/home/deep/liquid> cat info.rkt
#lang info
(define collection 'multi)
(define deps '("liquid-lib"   "liquid-doc"))
(define implies '("liquid-lib"   "liquid-doc"))
(define pkg-desc "Framework for developing experimental deep web search engines.")
(define pkg-authors '(twlynch))

I placed my racket file in liquid-lib:

§lambda1:/home/deep> ls liquid-lib
compiled  examples  info.rkt  liquid

§lambda1:/home/deep>  cat liquid-lib/info.rkt
#lang info
(define collection 'multi)
(define deps `("scheme-lib"  "base" ))
(define pkge-desc "implementation (no documentation) part of \"liquid\"")
(define pkg-authors '(twlynch))

§lambda1:/home/deep> ls liquid-lib/liquid
compiled        dbi-dblp.rkt         ...

I placed the scribble files in liquid-doc:

§lambda1:/home/deep> ls liquid-doc
example.scrbl  info.rkt  LICENSE.txt  liquid

§lambda1:/home/deep> cat liquid-doc/info.rkt
#lang info

(define collection 'multi)
(define deps '("base"))
(define build-deps '("scheme-lib"
                     "racket-doc"
                     "syntax-color-doc"
                     "liquid-lib"
                     "scribble-lib"))

(define pkg-desc "documentation part of \"liquid\"")

(define pkg-authors '(twlynch))

§lambda1:/home/deep> ls liquid-doc/liquid/
compiled      http-server.scrbl  liquid.scrbl         realtime.scrbl
db-lib.scrbl  info.rkt         query-parser.scrbl  tokens.scrbl

§lambda1:/home/deep> cat liquid-doc/liquid/liquid.scrbl
#lang scribble/doc
<at> (require scribble/manual scribble/struct scribble/xref
          (for-label scheme/base
                     scheme/contract
                     liquid/db-lib
                     ))

<at> title{LIQUID -- Framework for Developing Deep Web Search Programs and Servers}

<at> author["Thomas Walker Lynch and Andrea Calì"]

<at> table-of-contents[]

<at> include-section{"db-lib.scrbl"}
<at> include-section{"http-server.scrbl"}
<at> include-section{"query-parser.scrbl"}
<at> include-section{"realtime.scrbl"}
<at> include-section{"tokens.scrbl"}

questions:-----------------------------------------------------------------------------------

1. when trying to make the new package locally.  .. so what is the proper way to handle the dependencies?  I don't know if I should run raco pkg install on the liquid-doc and liquid-lib directories first, but haven't done that because I want these to be auto loaded and not directly in the catalog.


§lambda1:/home/deep/liquid> raco pkg install
raco pkg install: missing dependencies;
 specify `--deps search-auto' to install them, or
 specify `--deps search-ask' to be asked about installing them
  for package: /home/deep/liquid/
  missing packages:
   liquid-lib
   liquid-doc

2. when trying to build the docs standalone .. so how can one do this?

§lambda1:/home/deep/liquid-doc/liquid> scribble --htmls liquid.scrb
default-load-handler: cannot open module file
  module path: #<path:/home/deep/liquid-doc/liquid/liquid.scrb>
  path: /home/deep/liquid-doc/liquid/liquid.scrb
  system error: No such file or directory; errno=2
  context...:
   standard-module-name-resolver
   /usr/share/racket/pkgs/scribble-lib/scribble/run.rkt: [running body]

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to racket-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/61e73c39-8295-442a-8a69-814ce863f013%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Alexander D. Knauth | 16 Apr 23:25 2015

Re: try the new macro expander


On Apr 16, 2015, at 5:01 PM, Jos Koot <jos.koot@...> wrote:

> But:
> 
> (define quasiquote list)
> (car '`x) ; -> quasiquote as well, which is not obvious.
> 
> Racket has become very far in hygienic macros.
> Is is time to think about hygienic read-tables too?
> I have no idea how to acccomplish that. Sorry.

I think that even if the backquote where a “hygienic” reader macro, this would still produce ‘quasiquote.

That’s because `x would read as (quasiquote x), where quasiquote is bound to, well, who cares what it’s
bound to, it’s quoted as a symbol.

But if it’s not quoted then:
For an unhygienic backquote reader macro:
(define quasiquote list)
(define x 5)
`x ; -> (quasiquote x), where quasiquote is bound to the definition above -> (list x) -> (list 5) -> ‘(5)
For a hygienic backquote reader macro:
(define quasiquote list)
(define x 5)
`x ; -> (quasiquote x), where quasiquote is bound to quasiquote from racket -> ‘x

This already works in some cases with the current macro expander, if I extend the readtable with a mapping of
the backquote character to a procedure that returns a syntax object that has lexical context telling it
where the quasiquote identifier came from.  But with the current macro expander, there are many cases
where hygienic reader macros won’t work properly, which Matthew Flatt pointed out.

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/26C66189-56C6-4BCB-AC36-C54AA1582E0C%40knauth.org.
For more options, visit https://groups.google.com/d/optout.

Alexander D. Knauth | 16 Apr 22:26 2015

Re: try the new macro expander

The problem is that the backquote character is an unhygienic reader macro.  
But it was intended to work that way as an abbreviation, so that’s why it's not a problem.  

On Apr 16, 2015, at 4:09 PM, Jos Koot <jos.koot@...> wrote:

> I tried it and it works as I expected.
> So what is the problem?
> Jos Koot
> 
> -----Original Message-----
> From: gus.massa@...
[mailto:gus.massa@...] On Behalf Of Gustavo
> Massaccesi
> Sent: jueves, 16 de abril de 2015 21:59
> To: Alexander D. Knauth
> Cc: Matthew Flatt; Racket Devs
> Subject: Re: [racket-dev] try the new macro expander
> 
> Just for fun. Don't try this at home:
> 
> #lang racket
> (define-syntax-rule (quasiquote x) (reverse 'x))
> `(1 2 3 4)
> 
> Gustavo
> 
> -- 
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+unsubscribe@...
> To post to this group, send email to racket-dev@...
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/CAPaha9MC%2BruE_BpfLmBFW6nsktOj
> 0uRB6VUEHqRBpfXpaOPYdQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/A10D553B-CFD5-4F92-9247-5B4DA5DA145D%40knauth.org.
For more options, visit https://groups.google.com/d/optout.

Neil Van Dyke | 15 Apr 04:44 2015
Picon

html manual formatting plan

Are there any plans to fix issues with the new HTML documentation format 
in the near future?

I'm looking at the 6.1.1 documentation on `docs.racket-lang.org`. I've 
mentioned most of these issues before:

1. The CSS is still using font sizes for body text other than what the 
user has set their browser to use as their preferred size for reading 
body text.  This can make the font size too small for some people.  
(It's going out of its way to violate a 20 year-old standard, like it 
really hates ADA people and device independence.) For other people, this 
can result in less text being shown than people want, with the very 
limited screen real estate they have. (Say, when you're trying to keep 
one or more editor windows, documentation window, application window in 
view on a screen at the same time, but the CSS decides it knows better 
than the user and device what body font size to use.)

2. The CSS is still varying the font size dynamically in suboptimal 
ways.  For example, making the window wider can result in *less* text 
being shown, which is a problem for some types of reading we do from 
manuals.  (Go to a TOC page, drag out the width of the window, and watch 
how number of TOC entries visible "throbs" up and down, for no good 
reason.)   Another problem is the overhead from people having to 
constantly adjust to different text sizes.  (Go read a page of text in a 
larger than normal size, and then go read in normal size, and notice 
that the normal text seems small and takes some moments to adjust.  
Consider that you might be able to use that compute power and 
distraction for better purposes than tolerating ill-behaved CSS.)

3. The CSS is still conflating links for different purposes, such as for 
terminology, which used to be distinguished visually.  This throws away 
important information.

4. By default, when I format the documentation for a package, I'm now 
getting absolute URLs to CSS files that are potentially specific to the 
Scribble version that generated the HTML.  With the previous HTML 
format, by default I was getting relative URLs and fewer CSS and JS 
files, so I could just copy them to my Web site without modification, as 
the Web page for the package they document.  (Maybe there are options to 
work around the undesirable defaults?)

I'm asking not only because of usability and accessibility, but also 
because I need to mess with generated documentation as part of moving to 
the new package system.  I don't want to spend my limited time kludging 
around new infrastructure changes, before I can release more open source 
packages/updates, especially if the infrastructure is just going to 
change out from under me again.

Neil V.

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/552DD0AA.7010400%40neilvandyke.org.
For more options, visit https://groups.google.com/d/optout.

Matthew Flatt | 13 Apr 14:40 2015
Picon

try the new macro expander

The new macro expander is ready for you to try:

  http://www.cs.utah.edu/~mflatt/tmp/scope-snapshot/

What you should expect:

 * If your library has no macros, or if it uses only pattern-matching
   macros that don't expand to submodules or units, then it should work
   with the new expander without changes.

 * If your library includes a macro that expands to a submodule, then
   there's a good chance that the macro will need to change. The old
   expander allowed even pattern-based macros to generate submodules
   that bind parts of the macro's input. More generally, the new
   expander doesn't throw away as much pre-expanded context on a
   submodule form as the old expander.

 * If your library includes a macro that expands to a unit, and if a
   signature or definition are not both introduced by the macro or from
   the macro use site, then you might run into an unbound-identifier or
   missing-definition error. It's difficult to pin down what the old
   macro did, and in the few cases where I've seen a difference between
   the old and new version, I've been inclined to say that the old
   behavior was wrong. This change could be enough of a problem that we
   have to do something different, through, so please let me know if
   you run into it.

 * A macro that uses `syntax-local-get-shadower` like will have to be
   revised, and it should be revised to avoid that function. A macro
   that uses `syntax-local-make-delta-introducer` definitely will have
   to be revised, because that function is no longer supported. Most
   macros don't use such obscure functions.

Most packages build ok using the above snapshot:

 http://next-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/

Several failures are "ambiguous binding" errors. That error usually
indicates an unavoidable incompatibility between the old and new macro
systems. I'm interested to hear whether the package authors can
understand the errors and fix them and whether the incompatibilities
seem manageable.

(Thanks to Greg for fixing a problem in the "rackjure" package before
the build. That problem was due to a failure of the old macro expander
to report an import--definition conflict.)

If you're prefer to work from the "scope" branch of

   https://github.com/mflatt/racket

then it's simplest to add the catalog

   http://www.cs.utah.edu/~mflatt/tmp/scope-snapshot/catalog/

before "http://pkgs.racket-lang.org/" so that you get compatible
versions of the handful of packages that I modified.

I've also updated the write-up at

  http://www.cs.utah.edu/~mflatt/scope-sets-4/

The changes are relatively small and mostly in section 9.

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/20150413124050.89B946501BF%40mail-svr1.cs.utah.edu.
For more options, visit https://groups.google.com/d/optout.

Ryan Culpepper | 10 Apr 19:02 2015

Pre-Release Checklist for v6.2

Reminder: This is a practice release. The new release process is
described at:

   https://github.com/plt/racket/wiki/Release-process

Checklist items for the v6.2 release
   (using the v6.1.90.900 release candidate build)

Search for your name to find relevant items, reply when you finish an
item (please indicate which item/s is/are done).  Also, if you have any
commits that should have been picked, make sure that the changes are in.

Important: new builds are created without announcement, usually whenever
I pick a few commits.  If you need to commit changes, please make sure
you tell me to pick it into the release branch.

--> Release candidates are at
-->   http://pre-release.racket-lang.org

Please use these installers (or source bundles) -- don't test from
your own git clone (don't test the `master' branch by mistake!).  To
get the tests, you can do this:

   cd ...racket-root...
   ./bin/raco pkg install -i main-distribution-test

----------------------------------------------------------------------

* Matthew Flatt <mflatt@...>
   - R6RS Tests
   - Run the unix installer tests
   Updates:
   - Racket Updates: update HISTORY
   (updates should show v6.2 as the most current version)

* Robby Findler <robby@...>
   - DrRacket Tests

* Sam Tobin-Hochstadt <samth@...>,
    Vincent St-Amour <stamourv@...>
   - Typed Racket Updates: update HISTORY
   (updates should show v6.2 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Matthias Felleisen <matthias@...>
   - Teachpacks Tests: check that new teachpacks are addable
   - Teachpack Docs: check teachpack docs in the bundles
   - Try teaching-languages testing framework (check-expect)
   Updates:
   - Teachpack Updates: update HISTORY
   (updates should show v6.2 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Ryan Culpepper <ryanc@...>
   - Macro Debugger Tests
   - syntax-parse Tests
   - RackUnit GUI Tests
   - Data Tests
   - DB Tests
   - Rackunit Tests
   - SRFI Tests
   Release tests for (one of the) linux releases:
   - Test that the `racket' and `racket-textual' source releases
     compile fine (note that they're still called `plt' and `mz' at
     this stage).
   - Test that the binary installers for both work, try each one in
     both normal and unix-style installation modes. (just ubuntu)
   [Note: get the release candidates from the URL in this email. Use
    the 'static table' link to see a list of all tar files available]

* Stevie Strickland <sstrickl@...>
   - Unit Contract Tests
   - Contract Region Tests
   - Class Contract Tests

* Stephen Bloch <sbloch@...>
   - Picturing Programs Tests

* David Van Horn <dvanhorn@...>
   - EoPL Tests

* Neil Toronto <neil.toronto@...>
   - Plot Tests

* Doug Williams <m.douglas.williams@...>
   - Additional Plot Tests

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/55280211.5050403%40ccs.neu.edu.
For more options, visit https://groups.google.com/d/optout.

Sam Tobin-Hochstadt | 10 Apr 02:06 2015
Picon
Picon

Initial bug migration

Summary: if you get a lot of email from github about bugs, do not be alarmed.

I've started migrating bugs from our installation of Gnats to GitHub.
I've begun with Typed Racket bugs, because I know those best, and
because the TR developers are already using Github bugs.

You can see what the migrated bugs look like here:
https://github.com/racket/typed-racket/issues?q=label%3Agnats-migrated

The migrated bugs will be closed automatically soon.

If you haven't previously, go here: http://huor.soic.indiana.edu:8080/
to authorize me to post bugs and comments as you as part of the
migration.

Gnats is still working, and will be for a while. The next step will be
finishing the Typed Racket bug migration, and enabling (optionally)
submitting bugs to GitHub from inside DrRacket. Once that's done, I'll
move to other components of Racket.

Let me know if you have any questions about this, or you have feedback
about the process, or anything else.

Sam, bug czar

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BZEh8rKd0bo20p7S8m5jJSojXP1u%2BCTPHoFysKSs8RCuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

cyrille.deuss | 8 Apr 22:30 2015
Picon

bad symlink in linux

Hello

the /usr/share/pixmaps/plt* icons are symlinked to ../racket/collects/icons/plt* and should be to ../racket/pkgs/icons/plt* (/usr/share/racket/pkgs/icons/)

Sincerely yous

Cyrille DEUSS

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to racket-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/648d92db-d342-485a-ad32-7417c361061f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ryan Culpepper | 1 Apr 21:56 2015

Pre-Release Checklist for v6.2

Reminder: This is a practice release. The new release process is
described at:

   https://github.com/plt/racket/wiki/Release-process

Checklist items for the v6.2 release
   (using the v6.1.90.900 release candidate build)

Search for your name to find relevant items, reply when you finish an
item (please indicate which item/s is/are done).  Also, if you have any
commits that should have been picked, make sure that the changes are in.

Important: new builds are created without announcement, usually whenever
I pick a few commits.  If you need to commit changes, please make sure
you tell me to pick it into the release branch.

--> Release candidates are at
-->   http://pre-release.racket-lang.org

Please use these installers (or source bundles) -- don't test from
your own git clone (don't test the `master' branch by mistake!).  To
get the tests, you can do this:

   cd ...racket-root...
   ./bin/raco pkg install -i main-distribution-test

----------------------------------------------------------------------

* Matthew Flatt <mflatt@...>
   - Racket Tests
   - Languages Tests
   - GRacket Tests (Also check that `gracket -z' and `gracket-text' still
     works in Windows and Mac OS X)
   - mzc --exe tests
   - .plt-packing Tests
   - Games Tests
   - Unit Tests
   - Syntax Color Tests
   - R6RS Tests
   - JPR's test suite
   - Create an executable from a BSL program
   - Run COM tests
   - Embed-in-c test
   - Try compiling with -funsigned-char
   - Try compiling with TEST_ALTERNATE_TARGET_REGISTER
   - Run the unix installer tests
   Updates:
   - Racket Updates: update HISTORY
   (updates should show v6.2 as the most current version)
   - Update man pages in racket/man/man1: racket.1, gracket.1, raco.1
   Email me to pick the changes when they're done, or tell me if there
   are no such changes.

* Robby Findler <robby@...>
   - DrRacket Tests
   - Framework Tests
   - Contracts Tests
   - Games Tests
   - Teachpacks Tests: image tests
   - PLaneT Tests
   - Redex Tests
   Updates:
   - DrRacket Updates: update HISTORY
   - Redex Updates: update HISTORY
   (updates should show v6.2 as the most current version)
   - Ensure that previous version of DrRacket's preference files still
     starts up with new DrRacket
   - Update man pages in racket/man/man1: drracket.1
   Email me to pick the changes when they're done, or tell me if there
   are no such changes.

* John Clements <clements@...>
   - Stepper Tests
   Updates:
   - Stepper Updates: update HISTORY
   (updates should show v6.2 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Sam Tobin-Hochstadt <samth@...>,
    Vincent St-Amour <stamourv@...>
   - Match Tests
   - Typed Racket Tests
   - Typed Racket Updates: update HISTORY
   (updates should show v6.2 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Matthias Felleisen <matthias@...>
   - Teachpacks Tests: check that new teachpacks are addable
   - Teachpack Docs: check teachpack docs in the bundles
   - Try teaching-languages testing framework (check-expect)
   Updates:
   - Teachpack Updates: update HISTORY
   (updates should show v6.2 as the most current version; email me
   to pick the changes when they're done, or tell me if there are no such
   changes.)

* Ryan Culpepper <ryanc@...>
   - Macro Debugger Tests
   - syntax-parse Tests
   - RackUnit GUI Tests
   - Data Tests
   - DB Tests
   - Rackunit Tests
   - SRFI Tests

* Jay McCarthy <jay.mccarthy@...>
   - Web Server Tests
   - XML Tests
   - HTML Tests
   - PLAI Tests
   - Racklog tests
   - Datalog tests

* Stevie Strickland <sstrickl@...>
   - Unit Contract Tests
   - Contract Region Tests
   - Class Contract Tests

* Stephen Chang <stchang@...>
   - Lazy Racket Tests
   - Lazy stepper tests

* Stephen Bloch <sbloch@...>
   - Picturing Programs Tests

* Greg Cooper <greg@...>
   - FrTime Tests

* Jon Rafkind <rafkind@...>
   Release tests for (one of the) linux releases:
   - Test that the `racket' and `racket-textual' source releases
     compile fine (note that they're still called `plt' and `mz' at
     this stage).
   - Test that the binary installers for both work, try each one in
     both normal and unix-style installation modes. (just ubuntu)
   [Note: get the release candidates from the URL in this email. Use
    the 'static table' link to see a list of all tar files available]

* Mike Sperber <sperber@...>
   - DMdA Tests
   - Stepper Tests
   - Signature Tests

* David Van Horn <dvanhorn@...>
   - EoPL Tests

* Neil Toronto <neil.toronto@...>
   - Plot Tests
   - Images Tests
   - Inspect icons
   - Math tests

* Doug Williams <m.douglas.williams@...>
   - Additional Plot Tests

* Shriram Krishnamurthi <sk@...>
   Tour: check the tour and generate a new one if needed.
   [Note: Since this is a v6.1.90.900 build, you will need to edit your
     .../collects/framework/private/version.rkt
   file and change `(version)' to `"6.2"'.]

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/551C4D53.6000103%40ccs.neu.edu.
For more options, visit https://groups.google.com/d/optout.

Update text for planet.racket-lang.org?

The text for planet.racket-lang.org is a bit misleading; in particular, it starts with the claim that
"PLaneT is Racket's centralized package distribution system.” This is no longer the whole truth, and
it seems to me like we might want to gently steer users toward packages, ideally without scaring anyone
away entirely.

How about something like this set of edits:

DELETE: PLaneT is Racket's centralized package distribution system. Here you will find
user-contributed Racket packages along with instructions for using them.

REPLACE WITH: <i>Note:</i> Racket version 6.0 introduced a new package distribution system, whose home
page is <a>pkg.racket-lang.org</a>. Most recent development work uses this newer framework, and many
of the packages available on this page have newer versions as part of the new system. This page contains the
packages associated with Racket’s older package system, PLaneT.

AND: The Racket team is committed to a smooth transition, and the existing PLaneT infrastructure should be
supported for some time to come.

The packages on this site are user-contributed and not part of Racket. Be aware that when you download one of
them for use in your programs, you are installing software on your computer that could deliberately or
accidentally harm your system. Do not require from PLaneT any packages you do not trust.

DELETE: For more about how to use PLaneT and for instructions on turning your own code into packages, see the
PLaneT documentation (also available in your local installation).

This page shows the latest versions of all available packages, sorted by category.

DELETE: You can be notified when new packages are added by subscribing to the RSS feed or to the
PLaneT-Announce mailing list.

That’s how I think I would edit it, anyhow.

Neil, I think you’re probably the one most affected by this (proposed) change….

Thoughts?

John

--

-- 
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscribe@...
To post to this group, send email to racket-dev@...
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/89F262C8-E694-4AF6-8A17-EFCC1DF3DB8D%40brinckerhoff.org.
For more options, visit https://groups.google.com/d/optout.


Gmane