Overview of changes:
* Fixed version directive lookup
mkit.ini would be refused if version directive was at the end of the
file, while first and last 3 lines is what was supposed to work.
* Fixed license argument check
stub script would ignore license argument due to argument validation
error caused by refactoring.
* Fixed bad grep advice in MKIT_STUB_README.md
* Updated own dogfood
Overview of changes:
* Rewrote *newstub* as *stub* meta-command, now with update mode
The script looks promising, let's use the extensible CLI scheme.
* Removed sorting from `ini lskeys`
*stub* can rewrite user's mkit.ini but it does not want to mess it
up more than is necessary.
* User can now override project version with *stub*
* *stub* now Respects MKIT_INI environment variable
* Fixed problems with LICENSE.md and README.md rewriting in *stub*
* Moved MKit version directive to end of file
* Improved MKit's own project README.md
'newstub' was not so far to being able to update meta-data based on
existing mkit.ini. However, in order to keep the CLI sane, it seems
better to switch to meta-command scheme.
Overview of changes:
* Added 'newstub', builder script to help with new projects
The script is intended to help start up new MKit project by generating
structure necessary for MKit to work, and instructing user which
parts to review and how.
* Fixed bug when skeletons could be deployed as part of directory
If directory targeted in [files] section contained .skel files, they
would get deployed along with built files.
* Code refactoring
Moved global variables to new vars.sh module, improved initialization
and importing code and added file headers.
* Improved patch importer utility
Overview of changes:
* Enabled rpmstuff and debstuff specific tokens
These can be used to (somewhat hackishly) try to mitigate
differenceds between distros.
* Fixed printing error message to stdout
* Fixed broken error message
* Big code cleanup
Only refactoring, but we needed to get up to date with style.
Decouple variable declarations so that each can have docstring.
In case of _relck() we also rename variable $relsrc to a more
context-specific term $oracle.
Overview of changes:
* Changelog will be included in tag annotation message.
The changelog generated by `vbump_*` target will be included in tag
annotation message. The annotation message is meant as release note
of sorts, so it makes sense to have the changelog there. (For
example, GitHub will use the message as release note on Releases tab
of a project.)