Use jag to determine which version of a package is...
# helpa
addshore
08/14/2025, 2:32 PMI have some docs that want to do copy paste instructions, and I dont want to update them every time a new version of a package is updated.
It is somehting like
Copy code
sh
mkdir my-x-project
cd my-x-project
jag pkg init
jag pkg install github.com/x-io/toit-x Copy code
sh
cp ./.packages/github.com/x-io/toit-x/v0.1.1/examples/eink.toit ./main.toitaddshore
08/14/2025, 2:33 PMls ./.packages/github.com/x-io/toit-x/ | sort -V | tail -n 1f
floitsch
08/14/2025, 2:33 PMI would definitely not rely on it. I'm in the process of rewriting the package manager (this time in Toit), and it won't (necessarily) follow the same directory conventions anymore.
floitsch
08/14/2025, 2:35 PMDepending on the tutorial you could just install a specific version of your package.
floitsch
08/14/2025, 2:35 PMthat would hardcode the version a bit earlier, but at least the steps would always work.
floitsch
08/14/2025, 2:40 PMFor now, you could use the package.lock file. That's how the compiler finds the packages:
Copy code
builder.join(package_dirs[i]);
builder.join(entry.url);
builder.join(entry.version);floitsch
08/14/2025, 2:41 PMAs I said: I intend to change this in the future. (using the URLs as path is problematic; especially on Windows)
a
addshore
08/14/2025, 2:49 PMVERSION=$(jag pkg search lightbug-io/toit-lightbug | awk '{print $3}')addshore
08/14/2025, 2:50 PMalthough now I'm depending on awk xD
f
floitsch
08/14/2025, 2:53 PMAnd you might also run into issues with the new version of
toit pkgfloitsch
08/14/2025, 2:53 PMThe output might change.