-
Notifications
You must be signed in to change notification settings - Fork 243
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
Tweak rockspec to normalize fields, callout spec version, etc. #357
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,6 @@ | ||
rockspec_format = "3.0" | ||
package = "penlight" | ||
version = "scm-3" | ||
version = "dev-1" | ||
|
||
source = { | ||
url = "git://github.com/lunarmodules/Penlight.git", | ||
|
@@ -8,17 +9,20 @@ source = { | |
|
||
description = { | ||
summary = "Lua utility libraries loosely based on the Python standard libraries", | ||
homepage = "https://lunarmodules.github.io/Penlight", | ||
detailed = [[ | ||
Penlight is a set of pure Lua libraries focusing on input data handling | ||
(such as reading configuration files), functional programming | ||
(such as map, reduce, placeholder expressions,etc), and OS path management. | ||
Much of the functionality is inspired by the Python standard libraries. | ||
]], | ||
license = "MIT/X11", | ||
homepage = "https://lunarmodules.github.io/Penlight", | ||
issues_url = "https://github.com/lunarmodules/Penlight/issues", | ||
maintainer = "[email protected]", | ||
detailed = [[ | ||
Penlight is a set of pure Lua libraries for making it easier to work with common tasks like | ||
iterating over directories, reading configuration files and the like. Provides functional operations | ||
on tables and sequences. | ||
]] | ||
} | ||
|
||
dependencies = { | ||
"lua >= 5.1", | ||
"luafilesystem" | ||
} | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is ok for the DEV one, not sure about the release ones, since older luarocks installs will not be able to install Penlight anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay. Are you sure that's actually how it works? I thought some fields were just ignored if it doesn't understand them. If we have to strip out the test stuff (see #358) for the release rockspecs I guess that's workable, but it should still be in the dev one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the upshot is that for best compatibility we need to release stable versions using an older rockspec version ... which means dropping a couple of fields such as the testing definitions when the rockspec gets copied to stable tagged versions. If I'm understanding that right that shouldn't be too much of a problem, but it might be nice to automate that (or at least write a release checklist so we do it consistently).
Is there something I'm missing? Not having test runner information in the rockspec doesn't seem like a problem for stable release rockspecs, and personally I don't have a whole lot of sympathy for people trying to install bleeding edge Git HEAD software using very old tooling (2.4.3 is over 3 years and 15 releases old).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrt
see https://github.com/lunarmodules/Penlight/blob/master/CONTRIBUTING.md#release-instructions-for-a-new-version which is referred to from the changelog as well