25.03.2016 22:48, Adriano dos Santos Fernandes пишет:
> Em 25/03/2016 16:24, Dmitry Yemanov escreveu:
>> This gives us a buildno counted in days, not in commits (as now).
>>
> In practive it's not different.
>
> Doesn't the script is running per day like was in svn?
>
> Right, that means the snaps
On Sat, Mar 26, 2016 at 12:43:11PM +0300, alex wrote:
>
> 25.03.2016 22:48, Adriano dos Santos Fernandes пишет:
> > Em 25/03/2016 16:24, Dmitry Yemanov escreveu:
> >> This gives us a buildno counted in days, not in commits (as now).
> >>
> > In practive it's not different.
> >
> > Doesn't the scri
Em 26/03/2016 07:05, Michal Kubecek escreveu:
> On Sat, Mar 26, 2016 at 12:43:11PM +0300, alex wrote:
>>
>> 25.03.2016 22:48, Adriano dos Santos Fernandes пишет:
>>> Em 25/03/2016 16:24, Dmitry Yemanov escreveu:
This gives us a buildno counted in days, not in commits (as now).
>>> In prac
solution. For our own builds, both official
and snapshots, calculate the build number as commit count (as now, but
without storing in the repo). For external builds, gather LAST_COMMIT
and embed it into the version string *as date*. I.e. something like:
Firebird-4.0.0.123-Unstable (officia
25.03.2016 12:43, Dimitry Sibiryakov wrote:
> 25.03.2016 10:37, Dmitry Yemanov wrote:
>> We used exactly the same approach with SVN and nobody complained about
>> polluted changelog.
>
> Because nighty commits weren't in ChangeLog and nobody cared about native SVN
> log.
Just for the record - b
26.03.2016 17:43, Dmitry Yemanov wrote:
> 25.03.2016 12:43, Dimitry Sibiryakov wrote:
>
>> 25.03.2016 10:37, Dmitry Yemanov wrote:
>>> We used exactly the same approach with SVN and nobody complained about
>>> polluted changelog.
>>
>> Because nighty commits weren't in ChangeLog and nobody cared a
bed it into the version string *as date*. I.e. something like:
>
> Firebird-4.0.0.123-Unstable (official)
> vs
> Firebird-4.0.0.0-20160326-Unstable (unofficial)
>
> Port maintainers will either use our git-based scripts to get a proper
> build number or fix the version string t
26.03.2016 19:08, Adriano dos Santos Fernandes wrote:
>
> The problem I see is the executable version info which will not be accurate.
Please elaborate. Our executables will have build number in the
executable version info, as they always had.
> I like to see the commit hash in the string, even
Em 26/03/2016 13:22, Dmitry Yemanov escreveu:
> 26.03.2016 19:08, Adriano dos Santos Fernandes wrote:
>>
>> The problem I see is the executable version info which will not be accurate.
>
> Please elaborate. Our executables will have build number in the
> executable version info, as they always ha
Hi!
Can't we replace this script by git archive command?
Adriano
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
htt
10 matches
Mail list logo
