Re: Upcoming Ledger Release

[Alexis]

Hello Martin,
thank you for your test report and opinion on the versioning.

I'm glad to hear that all of the official and your personal test pass.


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Alexis]

Hi John,
  
apologies if my mail came across the wrong way. It was written with 
  
the notion that I myself could do more to help improve ledger and   
  
move it forward.
  

  
I'm keeping an eye on ledger's build compatibility on Mac using 
  
Homebrew, which is fairly quick with the latest Boost versions. 
  

  
Also every build of the master branch on Travis CI will use 
  
the required minimum Boost version, i.e. 1.49.0,
  
all other non-master builds will use the latest 
  
Boost version configured in .travis.yml, currently 1.60.0.  
  

  
So there is a little automated help for testing the ledger build
  
against different versions of boost.
  

  
Off-topic question: Did you attend http://conf.nixos.org ?  
  
Too bad I missed it…
  

  

  
Cheers, 
  
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Alexis]

Hello Juergen,
thanks for the report and taking the time to test the latest changes.

The boost build warnings you mentioned (and that I see also)
are a boost issue (see https://github.com/boostorg/iostreams/pull/24).


Cheers,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[John Wiegley]

> Alexis   writes:

> Apologies if my mail came across the wrong way. It was written with the
> notion that I myself could do more to help improve ledger and move it
> forward.

No worries, Alexis!

> Off-topic question: Did you attend http://conf.nixos.org ? Too bad I missed
> it…

No, I missed it also.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Juergen Daubert]

On Sat, Jan 02, 2016 at 02:01:05PM +0100, Alexis wrote:
> Hello everyone,
> a while ago I wanted to publish a new ledger release, but didn't
> (and I'd rather not have you asking why ;)
> 
> Ledger's bitrot is becoming more and more of a problem (especially with
> newer boost versions, namely 1.58, 1.59, and 1.60)
> so I think a new release is quite necessary.
> 
> I pushed the latest changes to the next and the release/3.1.1 branch
> and kindly ask that anyone willing to spend some time and effort
> test those changes and report any issues.

Testing the latest version from git I get a lot of the following
warnings with boost 1.60 but not with boost 1.59:

/usr/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: 
note: #pragma message: NOTE: Use of this header (template_arity_spec.hpp) is 
deprecated

and 

/usr/include/boost/type_traits/detail/bool_trait_def.hpp:18:79: note:
#pragma message: NOTE: Use of this header (bool_trait_def.hpp) is deprecated


However the build finshes with a working binary.
System: CRUX Linux system with gcc 5.3.0


Greetings
Juergen

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Martin Michlmayr]

* John Wiegley  [2016-01-02 09:02]:
> Why would it be named 3.2? Does it have any new features or change any APIs?
> 3.1.1 sounds like the correct number to me.

There's at least the new --no-revalued option and support for newer
Boost.  See doc/NEWS for a (probably incomplete) list of changes.

I'm for 3.2 due to some new features and the number of bug fixes, but
3.1.1 is fine with me.

I don't think the version number matters as much as getting a new
release out.

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Martin Michlmayr]

* Alexis  [2016-01-02 14:01]:
> To test ledger please:

I'm on Debian 8.2 with boost 1.55.0.2.  All ledger tests pass.

Furthermore, the test suite of my personal finance system going back
to 2008 passes.

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[John Wiegley]

> Alexis   writes:

> Ledger's bitrot is becoming more and more of a problem (especially with
> newer boost versions, namely 1.58, 1.59, and 1.60) so I think a new release
> is quite necessary.

Ledger's development proceeds at the pace of my needs -- since we don't have
others working on the C++ support, and I have many other matters demanding my
attention.

So, you can be certain it always works with the version of Boost supported by
Nix, since that's what I build it with. It's not actively "rotting". It's just
that we don't have someone dedicated to making it build with the latest Boost
on every possible platform. And I cannot be that person.

> Some folks wanted the next release to be numbered 3.2.0 instead of 3.1.1,
> and I'd like the community to decide. If you have an opinion on the matter
> please reply to this email and make your mark.

Why would it be named 3.2? Does it have any new features or change any APIs?
3.1.1 sounds like the correct number to me.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.