Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mruby
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
mruby
Commits
c9df4ccf
Commit
c9df4ccf
authored
Jun 22, 2014
by
take_cheeze
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update documentation of `summary` property of mrbgem spec.
parent
c43afd68
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
doc/mrbgems/README.md
doc/mrbgems/README.md
+4
-1
No files found.
doc/mrbgems/README.md
View file @
c9df4ccf
...
...
@@ -105,6 +105,7 @@ GEM directory. A typical GEM specification could look like this for example:
MRuby
::
Gem
::
Specification
.
new
(
'c_and_ruby_extension_example'
)
do
|
spec
|
spec
.
license
=
'MIT'
spec
.
author
=
'mruby developers'
spec
.
summary
=
'Example mrbgem using C and ruby'
end
```
...
...
@@ -119,7 +120,9 @@ information purpose:
*
`spec.author`
or
`spec.authors`
(Developer name or a list of them)
*
`spec.version`
(Current version)
*
`spec.description`
(Detailed description)
*
`spec.summary`
(Short summary)
*
`spec.summary`
*
One line short description of mrbgem.
*
Printed in build summary of rake when set.
*
`spec.homepage`
(Homepage)
*
`spec.requirements`
(External requirements as information for user)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment