how to use a package locally if not yet merged in pantry?

[mfts]

I had a discussion with @ddobrinskiy about testing / using a package locally that was built locally with pkg but not yet merged in the global pantry.

For example git3.sh

$ cd ~/pantry.extra
$ pkg build git3.sh
...
# builds binary successfully to tea.out/git3.sh

# open a new terminal in `cd $HOME`
$ TEA_PREFIX=~/pantry.extra/tea.out tea +git3.sh git3 --help
resolving package graph
error: not-found: pantry (spilt-tea-007)
no pantry: run `tea --sync`

Expectation

I expect that if I change the TEA_PREFIX to something where the package + binary already exists locally, it would work.

Interesting observation on what works:

$ cd ~/pantry.extra
$ TEA_PREFIX=~/dev/tea/pantry.extra/tea.out tea +git3.sh git3 --help
Usage: git3 [options] [command]

git3 mangement tool
...

[mxcl]

Interesting observation on what works

Run env | grep TEA_ and you will see why it works.

[mxcl]

This isn't really a bug, there literally is no pantry in your TEA_PREFIX. You would need to set TEA_PANTRY_PATH if you expect it to work which is why stepping into the pantry directory fixes it (its dev-env sets the pantry path).

I understand the pain. Perhaps I will come up with something that eases this. For now you can do:

TEA_DIR=~/pantry.extra tea git3 --help

I will leave it as an exercise for the reader on why this works.

[mfts]

Run env | grep TEA_ and you will see why it works.

Ok, I understand why it works from the pantry.extra directory but not anywhere else.

So setting these env variables, I expect it to work anywhere else

$ cd ~
$ TEA_PANTRY_PATH=/Users/mfts/dev/tea/pantry.extra tea git3 --help 
resolving package graph
error: http (spilt-tea-500)
403: https://dist.tea.xyz/git3.sh/darwin/aarch64/versions.txt

$ TEA_DIR=/Users/mfts/dev/tea/pantry.extra tea git3 --help 
tea: command not found: git3

I also tried it with both TEA_PREFIX and TEA_PANTRY_PATH

$ TEA_PANTRY_PATH=/Users/mfts/dev/tea/pantry.extra TEA_PREFIX=/Users/mfts/dev/tea/pantry.extra/tea.out tea git3 --help
resolving package graph
error: not found in pantry: nodejs.org (spilt-tea-005)

did you mean `nmap.org`? otherwise… see you on GitHub?

Not in pantry: nodejs.org

https://github.com/teaxyz/pantry.extra#contributing

nodejs.org is a runtime dep so I guess because it's in pantry.core and not pantry.extra, it's not found

Solution

Setting the pantry env variable to both pantry.extra, where git3.sh locally exists and the pantry from .tea where nodejs.org should exist, the result works! 🎉

$ TEA_PANTRY_PATH=/Users/mfts/dev/tea/pantry.extra:/Users/mfts/.tea/tea.xyz/var/pantry TEA_PREFIX=/Users/mfts/dev/tea/pantry.extra/tea.out tea git3 --help 
Usage: git3 [options] [command]

git3 mangement tool

[mxcl]

Setting TEA_DIR should work, otherwise it's a bug.

@mfts you'll find that your solution is setting the same vars as the dev-env does.

[mxcl]

Quite possibly setting an alternative TEA_PREFIX has no benefits. Worth considering. Then supplementing TEA_PANTRY_PATH would be enough to use working checkouts of the pantry and installs go to ~/.tea

[mfts]

Setting TEA_DIR should work, otherwise it's a bug.

Seems like it

$ TEA_DIR=/Users/mfts/dev/tea/pantry.extra tea git3 --help 
resolving package graph
error: http (spilt-tea-500)
403: https://dist.tea.xyz/git3.sh/darwin/aarch64/versions.txt

you'll find that your solution is setting the same vars as the dev-env does.

Yes, I copied the env | grep TEA_ from pantry.extra's dev-env

[mxcl]

K I know why setting TEA_DIR doesn't work, it's because it changes TEA_PREFIX which the active tea cannot handle.

$ TEA_DIR=/Users/mfts/dev/tea/pantry.extra tea tea git3 --help 
# ^^ probably works lol

[mfts]

Unfortunately, same error

$ TEA_DIR=/Users/mfts/dev/tea/pantry.extra tea tea git3 --help 
resolving package graph
error: http (spilt-tea-500)
403: https://dist.tea.xyz/git3.sh/darwin/aarch64/versions.txt

[mxcl]

New brewkit and pantries (not all released), installs everything to your standard TEA_PREFIX with builds in the pantry checkout.

This means TEA_PANTRY_PATH=pantry tea foo will work (or TEA_DIR=pantry tea foo) (and inside the dev-env just tea foo) (or ofc. just foo with magic)

Which is only marginally better, but it is a solution to this anyway.

Potentially we could cp the package.yml after builds. I dunno. Smells bad.

edit: or possibly this is the right solution since otherwise why are we installing to ~/.tea anyway? We could symlink it perhaps