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.

Sign up for GitHub

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

Jump to bottom

[SR-45] Package metadata in manifests #5403

Open
swift-ci opened this issue Dec 4, 2015 · 3 comments
Open

[SR-45] Package metadata in manifests #5403

swift-ci opened this issue Dec 4, 2015 · 3 comments

Comments

@swift-ci
Copy link
Contributor

swift-ci commented Dec 4, 2015

Previous ID SR-45
Radar rdar://problem/28171622
Original Reporter Dominik (JIRA User)
Type Improvement
Status Reopened
Resolution
Additional Detail from JIRA
Votes 2
Component/s Package Manager
Labels Improvement
Assignee None
Priority Medium

md5: 9eb80fc7b5fd544bda453d0d78c1c595

Issue Description:

Is it planned to add metadata to package manifests?

It would be great to be able to add some information about a package, which could then be exposed via the package manager (or i.e. a future "registry" webapp helping with discovery of packages, similar to e.g. [Packagist](https://packagist.org) for [Composer](https://getcomposer.org) packages. Composer is a php package manager).

Such metadata might contain stuff like:

  • package name

  • package description

  • package keywords (for search/discovery)

  • package homepage

  • license of the package

  • author(s) of the package

Maybe the [composer.json schema](https://getcomposer.org/doc/04-schema.md) is also worth a look in terms of inspiration.
@swift-ci
Copy link
Contributor Author

swift-ci commented Dec 4, 2015

Comment by Dominik (JIRA)

A little related to the metadata bit mentioned in SR-33.

@mxcl
Copy link
Contributor

mxcl commented Dec 7, 2015

Yes, though I am keen to reduce duplication so I'd like the standard to say eg. if the author is unspecified you should extract the author from the first commit in the repository, description could come from GitHub if the repo is on GitHub, etc.

I'm a believer that data should be determined automatically if possible, but overridable.

@abertelrud
Copy link
Contributor

I agree with Max's comment for the most part, though I do think there is value making it obvious to the author how they can declare intent. Inferring information is great as long as the source of the inference isn't so subtle that it causes confusion.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
@MarcelBochtler MarcelBochtler mentioned this issue Nov 25, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mxcl @tomerd @swift-ci @abertelrud