Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Include a .tea-meta file with installed packages #179

Open
ABevier opened this issue Jun 29, 2023 · 2 comments
Open

Feature Request: Include a .tea-meta file with installed packages #179

ABevier opened this issue Jun 29, 2023 · 2 comments

Comments

@ABevier
Copy link
Contributor

ABevier commented Jun 29, 2023

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:

  • when programmatically walking the tea install dir it becomes much easier to identify an installed package by the presence of this file
  • If the meta data file includes the a checksum of the installed package it can be used to determine if a package was yanked or rebuilt
  • Additional info from the pantry (display-name, dependencies, entry-point, etc) could be included in the meta file to prevent the need for additional pantry lookups.
@mxcl
Copy link
Member

mxcl commented Jul 2, 2023

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.

@mxcl
Copy link
Member

mxcl commented Sep 11, 2023

Should be called build-receipt.yml or something like that.

@mxcl mxcl transferred this issue from pkgxdev/pkgx Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants