This is for GCC 4.3 stabilisation. Thanks.
net-libs/aqbanking-2.3.3 which is stable, requires =0.8* of libofx, messy. Any way we could 1) stabilize a new aqbanking version OR 2) backport any GCC 4.3 compatibility patches to 0.8*? Option 1 is my preference.
(In reply to comment #1) > net-libs/aqbanking-2.3.3 which is stable, requires =0.8* of libofx, messy. Any > way we could 1) stabilize a new aqbanking version OR 2) backport any GCC 4.3 > compatibility patches to 0.8*? > > Option 1 is my preference. Thanks for the hint: Hanno, what do you think?
I'm not really comfortable with that, as aqbanking3 still lacks a commandline interface. There is though one in the works and I'll soon commit a package for it. The problem is, the aqbanking upstream breaks api with every version and now starts to make parts of it proprietary after api-breakages. Not nice, though that's the reason I wanted to keep aqbanking2 as the current stable for a while...
(In reply to comment #3) > I'm not really comfortable with that, as aqbanking3 still lacks a commandline > interface. > > There is though one in the works and I'll soon commit a package for it. > > The problem is, the aqbanking upstream breaks api with every version and now > starts to make parts of it proprietary after api-breakages. Not nice, though > that's the reason I wanted to keep aqbanking2 as the current stable for a > while... Please file a stable request for aqbanking3, nonetheless. Don't cc arches, but leave it open and make it block this bug and bug 245160 so we keep track of it. GCC 4.3 will have to wait anyway, we have lots of stable requests to handle. Another option is to backport the GCC 4.3 fix to the libofx-0.8.0 series...I won't.
Due to some wrong information I thought the only fix would have been stabilising 0.9.0. But an attentive user noticed it and filed a new bug to get 0.8.3 fixed...closing this bug.
