Splitting "foobar" into "foobar-lib", "foobar-doc", etc., certainly
solves the problem, and that approach is used widely for packages in
the main distribution. It's also kind of a pain, though, and
`--binary-lib` is intended to be a more automatic solution --- with the
trade-off that built packages need to be made available.
Yes, a script would need to traverse package dependencies. If you
already have the desired package installed somewhere, you should be
able to traverse packages in that installation.[*] Various functions
from `pkg/lib` and `setup/getinfo` can help implement the traversal,
including `pkg-directory`, `get-info`, and `extract-pkg-dependencies`.
[*] There's a potential issue with platform-specific dependencies, but
that's not an issue if the relevant packages tend are already
available in built form, as for the platform-specific packages in
the main distribution.
At Wed, 11 Nov 2015 10:03:00 +0100, Daniel Brunner wrote:
> Hi Matthew,
>
> thanks for your post and your hints. Now I have a better idea on what is
> going on. I managed to strip the packages with the "raco pkg create"
> command.
>
> But for a script .... hmmm... That script would need to check all
> dependencies on the target system then create the packages on a "build"
> system load them on the target system and install them? Or did I miss
> something?
>
> Wouldn't it be easier for me to split my packages in "foobar-lib" and
> "foobar-doc" packages to avoid the scribble dependencies coming on my box?
>
> Best wishes,
> Daniel
>
> Am 10.11.2015 um 15:57 schrieb Matthew Flatt:
> > You're trying the right thing, but it doesn't work because our
> > package-serving infrastructure didn't quite get there.
> >
> > Part of the idea was that the package-build service could provide built
> > versions of packages, and then you could install them from binary mode,
> > but built packages have not yet been made available that way. The
> > main-distribution's catalog does provide built versions of packages in
> > the main distribution. Other packages are currently only available in
> > source form --- at least from our servers --- and that's incompatible
> > with a binary install. (Also, the current error message is not good.)
> >
> > If you have the package installed somewhere, you could extract a built
> > version of the package using `raco pkg create --from-install`, and then
> > install the built package in `--binary-lib` mode on your target
> > environment. More generally, you could script the process of extracting
> > built packages and assembling them into a catalog. A tool like that
> > might be useful to others, too.
> >
> > At Tue, 10 Nov 2015 10:10:57 +0100, Daniel Brunner wrote:
> >> Hello,
> >>
> >> I have a minimal installation of Racket and want to install a package
> >> (Greg's aws package to name it) without its documentation. Otherwise
> >> packages are installed. In the "info.rkt" there are "deps" and
> >> "build-deps"
> >> (https://github.com/greghendershott/aws/blob/master/info.rkt). After
> >> reading raco's documentation I thought something like
> >>
> >> raco pkg install --binary-lib aws
> >>
> >> would give me only the code and not install scribble-lib etc. But it
> >> ends with an error:
> >>
> >> Resolving "aws" via http://download.racket-lang.org/releases/6.2.1/catalog/
> >> Resolving "aws" via http://pkgs.racket-lang.org
> >> Downloading
> >>
> https://github.com/greghendershott/aws/tarball/0167b4858f3ce4ee4574174699b5b1ce
> >> b1058c14
> >> raco pkg install: cannot strip directory in place
> >>
> >>
> >> Am I doing something wrong? Or is this the right way to come up with a
> >> installation without documentation?
> >>
> >> If not, the best way would be to seperate code/documentation in packages?
> >>
> >> Kind regards,
> >> Daniel
> >>
> >> --
> >> 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.
--
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.
