I stumbled over the following situation:
- I develop an app – so I’m in the app’s folder/environment (I used
pkg> initto set it up; wondering if I should use
pkg> generatesince the documentation does not say… but it seems that
pkg> generateshould be used for developing a new package, not for developing an app)
- I add a package and then do
- the package has a dependency,
ThePackageDep, which throws warnings / errors
Now say you want to fix these.
You can’t do
pkg> dev ThePackageDep in the app’s env – you actually have to do
pkg> dev ThePackage in the app’s environment. Then you have to go into
ThePackage and there do
pkg> dev ThePackageDep. I can imagine that it can be even more interesting if the problem is in a dependency of a dependency.
Also, for warnings, you can’t really tell where it’s coming from. Because there’s no call stack, so you don’t know whose dependency is throwing the warnings.
a. we can have something like
pkg> dev ThePackage > ThePackageDep which would do a nested
b. add a stack trace to warnings too