At Wed, 26 Jun 2013 01:04:13 -0400, Eli Barzilay wrote:
8 hours ago, Matthew Flatt wrote:
The config.rktd file in etc can now specify a location for the
installation-wide links.rktd file and pkgs installed-package
directory (with its pkgs.rktd).
On a clean build I get an empty etc
Two hours ago, Matthew Flatt wrote:
At Wed, 26 Jun 2013 01:04:13 -0400, Eli Barzilay wrote:
Furthermore, config.rktd can provide a list of additional
files/directories to search. This allows the main links.rktd
and pkgs to act like /usr/lib things, while additional
directories can act
Caveat 1: In case you don't use the top-level default `make' target
when building from the repo, this change means that you need to run
`make pkg-links' when you next update.
Caveat 2: Feel free to skip the rest. This message is on the far end of
what most of us care about in the package system.
On Tue, Jun 25, 2013 at 3:49 PM, Matthew Flatt mfl...@cs.utah.edu wrote:
Caveat 1: In case you don't use the top-level default `make' target
when building from the repo, this change means that you need to run
`make pkg-links' when you next update.
You may also find old, wrong version .zo
8 hours ago, Matthew Flatt wrote:
The config.rktd file in etc can now specify a location for the
installation-wide links.rktd file and pkgs installed-package
directory (with its pkgs.rktd).
On a clean build I get an empty etc directory -- explained by moving
the files that were in it -- but is
5 matches
Mail list logo
