[racket-users] catalog of built packages

[Matthew Flatt]

In case it's useful to anyone, the package-build service now provides
built versions of packages though this catalog:

  https://pkg-build.racket-lang.org/server/built/catalog/

Built packages can install faster than the source packages that are
provided by https://pkgs.racket-lang.org/ --- as long as you're using
the same version of Racket, which in this case is the current release.


For example, on my machine with version 6.4,

  raco pkg install --auto pict3d

takes about 8 minutes, but

  raco pkg install --auto \
   --catalog https://pkg-build.racket-lang.org/server/built/catalog/ \
   pict3d

takes about 20 seconds. Most packages build from source faster than
"pict3d", so the differences will not always be that large.


A built-package catalog is compatible with "binary library" install
mode. In that mode, sources and documentation are stripped away, and
dependencies that are needed only for compilation or building
documentation are not downloaded at all.


If you're running a version other than v6.4, the package-build catalog
is no better than the main source catalog, since installing a
v6.4-built package will rebuild, anyway. Also, if you're starting with
minimal Racket and only installing packages that are included in the
main distribution, then the default distribution-specific catalog
already provides packages as built.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [racket-users] catalog of built packages

['John Clements' via Racket Users]

> On Feb 10, 2016, at 7:04 AM, Matthew Flatt  wrote:
> 
> In case it's useful to anyone, the package-build service now provides
> built versions of packages though this catalog:
> 
>  https://pkg-build.racket-lang.org/server/built/catalog/
> 
> Built packages can install faster than the source packages that are
> provided by https://pkgs.racket-lang.org/ --- as long as you're using
> the same version of Racket, which in this case is the current release.

Excellent! Are there plans to make this a (checked) default, in the future, so 
that built packages are automatically downloaded if they’re compatible with the 
user’s version? I suppose in principle someone could have a package installed 
that changed the meaning of computation, which would invalidate this? 

John

> 
> 
> For example, on my machine with version 6.4,
> 
>  raco pkg install --auto pict3d
> 
> takes about 8 minutes, but
> 
>  raco pkg install --auto \
>   --catalog https://pkg-build.racket-lang.org/server/built/catalog/ \
>   pict3d
> 
> takes about 20 seconds. Most packages build from source faster than
> "pict3d", so the differences will not always be that large.
> 
> 
> A built-package catalog is compatible with "binary library" install
> mode. In that mode, sources and documentation are stripped away, and
> dependencies that are needed only for compilation or building
> documentation are not downloaded at all.
> 
> 
> If you're running a version other than v6.4, the package-build catalog
> is no better than the main source catalog, since installing a
> v6.4-built package will rebuild, anyway. Also, if you're starting with
> minimal Racket and only installing packages that are included in the
> main distribution, then the default distribution-specific catalog
> already provides packages as built.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.