Bug 2895 - git version missing in title bar
Summary: git version missing in title bar
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.9.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-03-21 18:19 UTC by Pierre Fortin
Modified: 2013-03-22 09:20 UTC (History)
2 users (show)

See Also:


Attachments
Snapshot build script (3.52 KB, application/octet-stream)
2013-03-22 09:20 UTC, Colin Leroy
no flags Details

Description Pierre Fortin 2013-03-21 18:19:21 UTC
Unless bug 2612 was implemented in git (I didn't find a hidden pref), git version number is no longer in title bar...  I'm obviously missing it... :)
Comment 1 Paul 2013-03-21 18:25:57 UTC
what do you see in the title bar? It all looks correct here.
Comment 2 Pierre Fortin 2013-03-21 18:40:40 UTC
<current_account> - Claws Mail 3.9.0

About: version 3.9.0-158-gb46954
Comment 3 Paul 2013-03-21 19:14:19 UTC
that's what's intended.
Comment 4 Pierre Fortin 2013-03-21 20:39:28 UTC
Then I'm puzzled why Christian Hesse opened enh. 2612; and the last CVS I compiled has:
  <current_accout - Claws Mail 3.9.0cvs122
Comment 5 brad@fineby.me.uk 2013-03-21 20:41:53 UTC
(In reply to comment #3)
> that's what's intended.

I /think/ Piere's expecting to see what I see in the title bar;

<current_account> - Claws Mail 3.9.0-158-gb46954


I believe he currently sees;

<current_account> - Claws Mail 3.9.0
Comment 6 Pierre Fortin 2013-03-21 20:46:02 UTC
Exactly Brad...  that begs the question: how did we both compile the exact same git version with different results...?
Comment 7 Paul 2013-03-21 20:47:53 UTC
(In reply to comment #5)
> (In reply to comment #3)
> > that's what's intended.
> 
> I /think/ Piere's expecting to see what I see in the title bar;
> 
> <current_account> - Claws Mail 3.9.0-158-gb46954
> 
> 
> I believe he currently sees;
> 
> <current_account> - Claws Mail 3.9.0

Yes, I understand that, but what he's seeing is what's intended. (He's built his Claws from one of the snapshot tarballs and not from git directly).
Comment 8 Pierre Fortin 2013-03-21 21:01:58 UTC
Good catch Paul!  Sorry about the noise then.  Now to go research what I need to do to use git...
Comment 9 Paul 2013-03-21 21:07:27 UTC
No problem, Pierre! I guess I should have been clearer in the first place!
Comment 10 brad@fineby.me.uk 2013-03-21 21:12:27 UTC
(In reply to comment #8)
> Good catch Paul!  Sorry about the noise then.  Now to go research what I
> need to do to use git...

Instructions are at;

http://www.claws-mail.org/git.php?section=projects

All remarkably easy, IMO.  Especially as I already had git installed.
Comment 11 Pierre Fortin 2013-03-21 21:49:42 UTC
Paul: no problem...  at least this "bug" can answer future queries...  :)

Brad: thanks.  I had written a new build script.  Turns out all I had to do was change the cvs checkout and update statements in my old script to the new git ones...

Just to close the loop: is there a generic script/other that you guys use to download|update, build & install?  Or do people all write their own?  Care to share if the former?
Comment 12 Colin Leroy 2013-03-22 09:06:34 UTC
the git version will show in title bar as long as one uses ./configure --enable-maintainer-mode, which is done automatically if using ./autogen.sh.

The git version is quite long and we didn't want to annoy release users with it.
Comment 13 Colin Leroy 2013-03-22 09:20:26 UTC
Created attachment 1248 [details]
Snapshot build script

Here's part of the snapshot script running on claws-mail.org (minus the web parts). It makes a full build then a minimal build and mails me if build's broken. A normal user update script could be trimmed down to

git reset --hard
git pull --all
./autogen.sh
make -j4
sudo make install

:)

Note You need to log in before you can comment on or make changes to this bug.