MantisBT - Ecere SDK
View Issue Details
0000714Ecere SDKinstallerpublic2012-03-28 18:312014-05-19 01:33
redj 
redj 
immediatefeatureN/A
closedfixed 
Cross-Platform\o/;-)
0.44 Ryoan-ji 
0.44.10 640.44.10 64 
0000714: Include Versioning information from git commit in releases during build
Include Versioning information from git commit in releases during build
No tags attached.
has duplicate 0000859closed redj Automatic git commit info 
Issue History
2012-03-28 18:31redjNew Issue
2012-03-29 07:55redjCategory => Installation System
2012-03-29 07:55redjProject@8@ => Ecere SDK
2012-03-29 08:15redjSummaryinstaller: automatic git commit info => automatic git commit info
2012-06-01 23:45jeromeSummaryautomatic git commit info => Include Versioning information from git commit in releases during build
2012-06-01 23:45jeromeDescription Updated
2013-10-06 17:58jeromeRelationship addedhas duplicate 0000859
2013-10-06 19:28jeromeTarget Version0.44.12 Fixes => 0.44.10 64
2013-10-06 19:29jeromeStatusnew => assigned
2013-10-06 19:29jeromeAssigned To => redj
2013-10-06 23:04redjStatusassigned => resolved
2013-10-06 23:04redjFixed in Version => 0.44.10 64
2013-10-06 23:04redjResolutionopen => fixed
2013-10-06 23:04redjNote Added: 0001125
2013-10-09 06:54jeromeNote Edited: 0001125
2013-10-09 07:00jeromeStatusresolved => closed
2013-10-09 07:12jeromeStatusclosed => resolved
2013-10-09 07:12jeromeNote Added: 0001130
2013-10-09 07:18jeromeNote Edited: 0001130
2013-10-09 17:40jeromeNote Added: 0001131
2013-10-19 05:10jeromeNote Added: 0001135
2013-10-19 05:36jeromeNote Deleted: 0001135
2013-12-01 20:58jeromeNote Added: 0001143
2013-12-01 20:58jeromeStatusresolved => assigned
2014-01-21 17:09redjStatusassigned => resolved
2014-01-21 19:19redjNote Added: 0001152
2014-01-23 10:29jeromeNote Added: 0001154
2014-01-23 10:29jeromeStatusresolved => assigned
2014-02-08 15:27redjStatusassigned => resolved
2014-05-19 01:33jeromeStatusresolved => closed

Notes
(0001125)
redj   
2013-10-06 23:04   
(edited on: 2013-10-09 06:54)
Fixed by:
https://github.com/ecere/ecere-sdk/commit/52149c1a51725d36dc5d7c5535cfc1d9d7aa043d [^]

(0001130)
jerome   
2013-10-09 07:12   
(edited on: 2013-10-09 07:18)
How will this work for:

- PPAs
- Debian/Ubuntu builds

Maybe we can handle this in the crossplatform.mk, considering this as a different VCS?

Maybe simply the folder name if git says it's not a git repository, rather than unknown? Looking for and stripping 'ecere-sdk-' :

The PPA would be something like: ecere-sdk-201310090150
the Debian build would say something like: ecere-sdk-0.44.10

(0001131)
jerome   
2013-10-09 17:40   
For PPA/Debian builds, we should probably look for a debian/ folder and read the Changelog.

The cwd approach will work for original source release tarballs.
(0001143)
jerome   
2013-12-01 20:58   
Reopened to address fixes required for the release:
- PPA/Debian builds
- Do not fail to build on git missing
(0001152)
redj   
2014-01-21 19:19   
fixed by https://github.com/redj/ecere-sdk/commit/d562ee08a433780c1e32b961bb8cd37c8c349a0f [^]
(0001154)
jerome   
2014-01-23 10:29   
We need a 'PACKAGE_NAME' so as not to hard-code 'ecere-sdk-' for the directory name detection, as this is the generated files for all projects not just the SDK...

Also, how to properly handle the fact that we have sub-projects deep within the SDK or main package directory? (And where is this PACKAGE_NAME going to be set?)