suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert "Changing the convention of referring to PLT in Planet 2 docs"

Browse Source 
This reverts commit 14c169623f4bcffd41d145dfed2bc8317b5faffc.
This commit is contained in:
Jay McCarthy 2012-11-08 20:43:10 -07:00
parent ec269fc1cf
commit fbed04db70
1 changed files with 23 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
collects/planet2/scribblings/planet2.scrbl
View File

@ -85,12 +85,12 @@ with a @racket[read]-able hash table with the keys: @racket['source]
bound to the source and @racket['checksum] bound to the bound to the source and @racket['checksum] bound to the
checksum. Typically, the source will be a remote URL string. checksum. Typically, the source will be a remote URL string.
The Racket maintainers supports two @tech{package name services}, PLT supports two @tech{package name services}, which are enabled by
which are enabled by default: @filepath{https://plt-etc.byu.edu:9004} default: @filepath{https://plt-etc.byu.edu:9004} for new Planet 2
for new Planet 2 packages and @filepath{https://plt-etc.byu.edu:9003} packages and @filepath{https://plt-etc.byu.edu:9003} for
for automatically generated Planet 2 packages for old Planet 1 automatically generated Planet 2 packages for old Planet 1
packages. Anyone may host their own @tech{package name service}. The packages. Anyone may host their own @tech{package name service}. The
source for the Racket-hosted servers is in the source for the PLT-hosted servers is in the
@racket[(build-path (find-collects-dir) "meta" "planet2-index")] @racket[(build-path (find-collects-dir) "meta" "planet2-index")]
directory. directory.
@ -383,14 +383,13 @@ Games, etc.}
@item{Packages are not allowed to start with @pkgname{plt}, @item{Packages are not allowed to start with @pkgname{plt},
@pkgname{racket}, or @pkgname{planet} without special approval from @pkgname{racket}, or @pkgname{planet} without special approval from
Planet 2 curation.} PLT curation.}
] ]
@section{Planet 1 Compatibility} @section{Planet 1 Compatibility}
The Racket maintainers run a Planet 1 compatibility @tech{package name PLT maintains a Planet 1 compatibility @tech{package name service} at
service} at
@link["https://plt-etc.byu.edu:9003/"]{https://plt-etc.byu.edu:9003/}. This @link["https://plt-etc.byu.edu:9003/"]{https://plt-etc.byu.edu:9003/}. This
PNS is included by default in the Planet search path. PNS is included by default in the Planet search path.
@ -564,7 +563,7 @@ responsive about fixing regressions against changes in Racket, etc.}
] ]
This categories will be curated by the Racket maintainers. This categories will be curated by PLT.
Our goal is for all packages to be in the @reponame{solar-system}, with Our goal is for all packages to be in the @reponame{solar-system}, with
the @reponame{galaxy} as a temporary place while the curators work with the the @reponame{galaxy} as a temporary place while the curators work with the
@ -583,12 +582,12 @@ the case that older packages have preference. (For example,
package used by both @pkgname{tic-tac-toe} and package used by both @pkgname{tic-tac-toe} and
@pkgname{factory-optimize}.) @pkgname{factory-optimize}.)
In contrast, the @reponame{planet} category will be a special category In contrast, the @reponame{planet} category will be a special category that
that authors may apply for. Admission requires a code audit and authors may apply for. Admission requires a code audit and implies
implies a "stamp of approval" from the Racket maintainers. In the a "stamp of approval" from PLT. In the future, packages in this
future, packages in this category will have more benefits, such as category will have more benefits, such as automatic regression testing
automatic regression testing on DrDr, testing during releases, on DrDr, testing during releases, provided binaries, and advertisement
provided binaries, and advertisement during installation. during installation.
The Planet 1 compatibility packages will also be included in The Planet 1 compatibility packages will also be included in
the @reponame{solar-system} category, automatically. the @reponame{solar-system} category, automatically.
@ -659,16 +658,16 @@ these included are painful to maintain and unreliable given users with
different versions of Racket installed. different versions of Racket installed.
One solution is to have a separate place where such "binary" packages One solution is to have a separate place where such "binary" packages
are available. For example, the Racket maintainers could run a PNS for are available. For example, PLT could run a PNS for every Racket
every Racket version, i.e., version, i.e., @filepath{https://binaries.racket-lang.org/5.3.1.4},
@filepath{https://binaries.racket-lang.org/5.3.1.4}, that would that would contain the binaries for all the packages in the
contain the binaries for all the packages in the @reponame{planet} @reponame{planet} category. Thus, when you install package
category. Thus, when you install package @pkgname{tic-tac-toe} you @pkgname{tic-tac-toe} you could also install the binary version from
could also install the binary version from the appropriate PNS. the appropriate PNS.
There are obvious problems with this... it could be expensive for the There are obvious problems with this... it could be expensive for PLT
Racket maintainers in terms of space and time... Racket compilation is in terms of space and time... Racket compilation is not necessarily
not necessarily deterministic or platform-independent. deterministic or platform-independent.
This problem requires more thought.} This problem requires more thought.}