You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes a wake package is split across multiple directories, or it has a name that is difficult to guess where in the directory hierarchy it might be. Inherently, a wake package name doesn't have to hint anything about where it's located.
Say we have package foo somewhere in a directory structure like:
Sometimes a wake package is split across multiple directories, or it has a name that is difficult to guess where in the directory hierarchy it might be. Inherently, a wake package name doesn't have to hint anything about where it's located.
Say we have
package foo
somewhere in a directory structure like:Is
package foo
infoo/
or injjj/bbb/foo-utils
? or both? nither?It could be nice to have some way to query where package files live, for example:
We can do this today with a shell snippet like:
The text was updated successfully, but these errors were encountered: