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

Package metadata #4

Open
Boris-Dimov opened this issue Jul 2, 2022 · 5 comments
Open

Package metadata #4

Boris-Dimov opened this issue Jul 2, 2022 · 5 comments
Labels
enhancement New feature or request ez pz lemon squeez Eaz to solv by new programmers future-proofing Dis feature ae gonna ease burdens in da futre help wanted Extra attention is needed
Milestone

Comments

@Boris-Dimov
Copy link
Contributor

Boris-Dimov commented Jul 2, 2022

I think every archive with a package should contain a simple text file, which describes things like name, version, dependencies, author etc. We just have to agree on a format, i.e. what it will contain.

Also it would be nice if the archive contained a list of where each file / directory should land, i.e. where in the FS it should be copied to.

This is just future-proofing stuff.

@Boris-Dimov Boris-Dimov added enhancement New feature or request ez pz lemon squeez Eaz to solv by new programmers help wanted Extra attention is needed future-proofing Dis feature ae gonna ease burdens in da futre labels Jul 2, 2022
@Kaper365
Copy link
Member

Kaper365 commented Jul 2, 2022

Imo we'd have to create a central database accessible under frue-project.org with a list of pkgs and their respective metadata

@Boris-Dimov
Copy link
Contributor Author

That too
But also every package should have it in itself, kinda like .deb packages

@Kaper365
Copy link
Member

Kaper365 commented Jul 2, 2022

I mean the fpkg utility would access the db and return metadata + download link and thus we wouldn't have to ship unnecessary stuff with packages

Metadata would be copied from remote db to a local fpkg-db with metadata of local packages

@Boris-Dimov
Copy link
Contributor Author

Let's do the metadata this way:
the file will contain entries in the way of
Key=Value

Mandatory entries will be:
PackageName=(self-explanatory)
Ver=(version)
Repo=(repository name)
RepoURL=(repository URL)
Description=(human-readable description)
FileList=(filename of the list of ordinary files)
ConfigsList=(filename of the list of configs)

Optional entries will be:
Author=(author name)
and others that y'all deem necessary

@Kaper365
Copy link
Member

Kaper365 commented Jul 5, 2022

Imo "Author" should be necessary, this way people'll be able to trace packages back to original author and it'd reduce suspicion of malicious packages

@Kaper365 Kaper365 added this to the ALPHA-1 milestone Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ez pz lemon squeez Eaz to solv by new programmers future-proofing Dis feature ae gonna ease burdens in da futre help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants