a user installs webppl by attaching the rwebppl package, so that it's stored in the package directory
they later decide that webppl is super useful and want to run bigger models on the command line so they run npm install -g webppl
In this case, they'll have separate installations for rwebppl and command-line webppl which could lead to some headaches (e.g. if they upgrade one, it won't upgrade the other...) One solution is to expose the link_webppl() function so that the user can replace the installation within rwebppl with a symlink to their global install.
There's a potentially messy situation where
rwebppl
package, so that it's stored in the package directorynpm install -g webppl
In this case, they'll have separate installations for
rwebppl
and command-line webppl which could lead to some headaches (e.g. if they upgrade one, it won't upgrade the other...) One solution is to expose thelink_webppl()
function so that the user can replace the installation withinrwebppl
with a symlink to their global install.