Open ABevier opened 1 year ago
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 useful.
All the same tho, it will also get out of data so gui shouldn't depend on it probs.
when programmatically walking the tea install dir it becomes much easier to identify an installed package by the presence of this file
well libtea should provide the function to do this anyway.
Should be called build-receipt.yml
or something like that.
When tea installs a package it would be nice if it included some sort of metadata dotfile in the install dir, perhaps called
.tea-meta
. This could be useful for a few reasons: