Mikhail == Mikhail Teterin [EMAIL PROTECTED] writes:
Mikhail Hello! Boost-1.34 is not only released now, it is also
Mikhail _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail current release of LyX (1.4.4) fails to build against it.
Mikhail I'm attaching the patch I plan to add
Jean-Marc Lasgouttes wrote:
Mikhail == Mikhail Teterin [EMAIL PROTECTED] writes:
Mikhail Hello! Boost-1.34 is not only released now, it is also
Mikhail _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail current release of LyX (1.4.4) fails to build against it.
Mikhail I'm
Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes:
Abdelrazak IIUC, this patch is to make LyX compile with external
Abdelrazak boost 1.34.0 which known to be deficient. Are you sure
Abdelrazak that this patch will work with our bundled boost?
OK, I agree that it would be better to avoid
Jean-Marc Lasgouttes wrote:
Mikhail == Mikhail Teterin [EMAIL PROTECTED] writes:
Mikhail Hello! Boost-1.34 is not only released now, it is also
Mikhail _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail current release of LyX (1.4.4) fails to build against it.
Mikhail == Mikhail T [EMAIL PROTECTED] writes:
Mikhail No, such bundling is wrong... Ensuring compatibility with two
Mikhail (or even three) most recent versions of Boost would,
Mikhail probably, be still easier for you, and would do The Right
Mikhail Thing (TM), instead of inflating your own
Mikhail T. wrote:
Jean-Marc Lasgouttes wrote:
This is exactly why we bundle boost with LyX :)
No, such bundling is wrong... Ensuring compatibility with two (or even
three) most recent versions of Boost would, probably, be still easier
for you, and would do The Right Thing (TM), instead
> "Mikhail" == Mikhail Teterin <[EMAIL PROTECTED]> writes:
Mikhail> Hello! Boost-1.34 is not only released now, it is also
Mikhail> _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail> current release of LyX (1.4.4) fails to build against it.
Mikhail> I'm attaching the patch I
Jean-Marc Lasgouttes wrote:
"Mikhail" == Mikhail Teterin <[EMAIL PROTECTED]> writes:
Mikhail> Hello! Boost-1.34 is not only released now, it is also
Mikhail> _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail> current release of LyX (1.4.4) fails to build against it.
Mikhail>
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> IIUC, this patch is to make LyX compile with external
Abdelrazak> boost 1.34.0 which known to be deficient. Are you sure
Abdelrazak> that this patch will work with our bundled boost?
OK, I agree that it would be
Jean-Marc Lasgouttes wrote:
"Mikhail" == Mikhail Teterin <[EMAIL PROTECTED]> writes:
Mikhail> Hello! Boost-1.34 is not only released now, it is also
Mikhail> _required_ for the upcoming LyX-1.5.0. Unfortunately, the
Mikhail> current release of LyX (1.4.4) fails to build against
> "Mikhail" == Mikhail T <[EMAIL PROTECTED]> writes:
Mikhail> No, such bundling is wrong... Ensuring compatibility with two
Mikhail> (or even three) most recent versions of Boost would,
Mikhail> probably, be still easier for you, and would do The Right
Mikhail> Thing (TM), instead of
Mikhail T. wrote:
Jean-Marc Lasgouttes wrote:
This is exactly why we bundle boost with LyX :)
No, such bundling is wrong... Ensuring compatibility with two (or even
three) most recent versions of Boost would, probably, be still easier
for you, and would do The Right Thing (TM), instead
Mikhail == Mikhail Teterin [EMAIL PROTECTED] writes:
Mikhail But do you intend to keep maintaining the two branches for a
Mikhail while? If so, I'll, probably, make a separate port of lyx15
Mikhail -- for the adventerous.
No, there is no plan to maintain 1.4 beyond 1.4.5 (unless something
> "Mikhail" == Mikhail Teterin <[EMAIL PROTECTED]> writes:
Mikhail> But do you intend to keep maintaining the two branches for a
Mikhail> while? If so, I'll, probably, make a separate port of lyx15
Mikhail> -- for the adventerous.
No, there is no plan to maintain 1.4 beyond 1.4.5 (unless
Hello!
Boost-1.34 is not only released now, it is also _required_ for the upcoming
LyX-1.5.0. Unfortunately, the current release of LyX (1.4.4) fails to build
against it.
I'm attaching the patch I plan to add to FreeBSD's print/lyx port to make the
source compatible with both Boost-1.33.1 and
You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it
has
too many invasive changes (such as removal of many front-ends) to be
immediately adopted...
I plan to release LyX 1.4.5 about at the same time as 1.5.0 (because it will
contain code
to read LyX 1.5.0 files). I'll
On п'ятниця 06 липень 2007, you wrote:
=
= You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it
= has
= too many invasive changes (such as removal of many front-ends) to be
= immediately adopted...
=
= I plan to release LyX 1.4.5 about at the same time as 1.5.0 (because
Hello!
Boost-1.34 is not only released now, it is also _required_ for the upcoming
LyX-1.5.0. Unfortunately, the current release of LyX (1.4.4) fails to build
against it.
I'm attaching the patch I plan to add to FreeBSD's print/lyx port to make the
source compatible with both Boost-1.33.1 and
> You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it
> has
> too many invasive changes (such as removal of many front-ends) to be
> immediately adopted...
I plan to release LyX 1.4.5 about at the same time as 1.5.0 (because it will
contain code
to read LyX 1.5.0 files).
On п'ятниця 06 липень 2007, you wrote:
=
= > You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it
= > has
= > too many invasive changes (such as removal of many front-ends) to be
= > immediately adopted...
=
= I plan to release LyX 1.4.5 about at the same time as 1.5.0
20 matches
Mail list logo
