Max Howell
Max Howell
Yeah that script needs an update, though probs just use the new two part system since it made the reason you created the `.py` version obsolete since you can control...
we don’t support `>` since it is ambiguous what the user means. eg. `> 1.2.3` will allow `1.2.3.1` but you probably mean `1.2.4` and above Probably the error message should...
What are you trying to achieve? A private separate pantry? Something else?
anything specific? We do validate a bunch of it. The audit step audits some parts and the general parsing infra the rest. I am sure there are exceptions but well…...
hah, interesting. Not really sure what we *should* do. User literally moved the dir. In this case we don’t care about the working directory anymore since it is the last...
Another reason to do this is any metadata we write would represent the metadata for that package at install time irrelevant of future changes to the pantry. Which can be...
Should be called `build-receipt.yml` or something like that.
While I agree this could be better there isn't actually any options here. There is one tea-prefix and one editable pantry (your clone). So if it's talking about a pantry...
I understand brewkit being scrappy is frustrating, but our resources are max’d out so we target the growth portions which is the tea/cli and the pantry. So brewkit is mainly...
Your request here seems simple right? That we show the path to the yaml for the project. Well the code to read the pantry is abstracted so it doesn't know...