After installation, the bundle script and info.jdn file end up having the
same parent directory under <syspath>/bundle.
Within the "repository root", the bundle script and info.jdn file are
allowed to not share a common parent:
bundle/init.janet
info.jdn
bundle/info.jdn
bundle.janet
However, it seems like these arrangements could lead to problems
because if the bundle script relies on the content of the info.jdn
file (e.g. via slurping and parseing), then the relative location
of the two files can matter. The bundle script needs to function
properly in both of its "homes" (i.e. when somewhere under the
repository root as well as when installed).
Thus it seems better to me to encourage one the following two arrangements instead:
bundle/init.janet
bundle/info.jdn
bundle.janet
info.jdn
ATM jeep new doesn't seem to do this:
$ ls -al
total 40
drwxrwxr-x 4 user user 4096 Nov 10 09:52 .
drwxr-xr-x 333 user user 16384 Nov 10 09:52 ..
drwxrwxr-x 2 user user 4096 Nov 10 09:52 bundle
-rw-rw-r-- 1 user user 109 Nov 10 09:52 .gitignore
-rw-rw-r-- 1 user user 332 Nov 10 09:52 info.jdn
-rw-rw-r-- 1 user user 262 Nov 10 09:52 README.md
drwxrwxr-x 2 user user 4096 Nov 10 09:52 test
$ ls bundle/
init.janet