Guenter Milde wrote:
> > Stating more than that sounds like overkill.
>
> I still favour specifying a required TeXLive version based on these
> considerations.
>
> If we take the conservative route, this would be TeXLive 2012 that ships
> with the current CentOS (v. 7).
Quickly skimming through
On 2015-10-30, Pavel Sanda wrote:
> Scott Kostyshak wrote:
>> Ah makes sense. Regarding for example Ubuntu LTS, how should we state
>> such a rule? If LyX has a major release on May 1st 2016 does that mean
>> we can depend on the latest versions in Ubuntu 16.04? That does not feel
>> correct. So th
Scott Kostyshak wrote:
> Ah makes sense. Regarding for example Ubuntu LTS, how should we state
> such a rule? If LyX has a major release on May 1st 2016 does that mean
> we can depend on the latest versions in Ubuntu 16.04? That does not feel
> correct. So then something like "6 months after an LTS
Richard Heck wrote:
> I guess my question then is what to do shorter term. It seems a bit late
> in the 2.2 cycle to do what we imagined above.
I don't think we need to do anything short-term. What we learned in this
discussion is that adding new styles to an existing layout can cause
problems
Guenter Milde wrote:
> On 2015-10-29, Georg Baum wrote:
>> What do you mean by supported?
>
> I meant the oldest LyX-supported version, in other words the minimal
> required version for flawless working with LyX.
I see, I misunderstood "supported" as "supported by the TeXLive team".
> For 2.2,
On Fri, Oct 30, 2015 at 11:27:58AM -0400, Richard Heck wrote:
> On 10/29/2015 12:48 AM, Scott Kostyshak wrote:
> >On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
> >>>2. Pavel's idea that for key dependencies such as Qt or TeX we should
> >>>look where stable/future versions on major
On 10/29/2015 05:10 PM, Georg Baum wrote:
Richard Heck wrote:
If we support the added style, then users who both use that style and
use an older version of the package will have non-compilable documents.
So you could have a document that worked perfectly well, you make one
change---use the new
On 10/29/2015 12:48 AM, Scott Kostyshak wrote:
On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
2. Pavel's idea that for key dependencies such as Qt or TeX we should
look where stable/future versions on major linux distros are. e.g.
stable debian. Another possibility is to look at t
On 2015-10-29, Georg Baum wrote:
> Guenter Milde wrote:
>1. A layout change can be made if it is supported by the current
>release of TeX Live and the previous release.
Actually also the pre-previous release (at least when I asked last time).
...
>>> I still think there is some use to
Richard Heck wrote:
> If we support the added style, then users who both use that style and
> use an older version of the package will have non-compilable documents.
> So you could have a document that worked perfectly well, you make one
> change---use the new style---and now it won't compile. Wha
Guenter Milde wrote:
> On 2015-10-29, Scott Kostyshak wrote:
>> On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
>>> On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
>>> >
>>> >It seems there are a few different ideas. Let me see if I can summarize
>>> >them:
>>> >
>>> >1. A layout chan
Richard Heck wrote:
> On 10/28/2015 03:59 PM, Scott Kostyshak wrote:
>> On Tue, Oct 27, 2015 at 01:29:51AM +0100, Uwe Stöhr wrote:
>>> Am 26.10.2015 um 22:42 schrieb Scott Kostyshak:
>>>
>>> - There are 2 sorts of layout issues that could violate the rule:
>>> 1. Layouts for journals: We often had
Uwe Stöhr wrote:
> Am 27.10.2015 um 20:32 schrieb Georg Baum:
>
>> I think LyX would be perfectly suitable for frequent updates in theory,
>> and I'd like to see those as well one day. For example, all those small
>> new features like the one we are discussing in this thread, would not
>> need to
On 2015-10-29, Scott Kostyshak wrote:
> On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
>> On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
>> >
>> >It seems there are a few different ideas. Let me see if I can summarize
>> >them:
>> >
>> >1. A layout change can be made if it is support
On Wed, Oct 28, 2015 at 08:52:32PM -0400, Richard Heck wrote:
> On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
> >
> >It seems there are a few different ideas. Let me see if I can summarize
> >them:
> >
> >1. A layout change can be made if it is supported by the current release
> >of TeX Live and t
On 10/28/2015 03:59 PM, Scott Kostyshak wrote:
On Tue, Oct 27, 2015 at 01:29:51AM +0100, Uwe Stöhr wrote:
Am 26.10.2015 um 22:42 schrieb Scott Kostyshak:
- There are 2 sorts of layout issues that could violate the rule:
1. Layouts for journals: We often had the discussion about this and my own
On 10/28/2015 03:52 PM, Scott Kostyshak wrote:
It seems there are a few different ideas. Let me see if I can summarize
them:
1. A layout change can be made if it is supported by the current release
of TeX Live and the previous release. This rule can be less strict if
the only change is an added
On Tue, Oct 27, 2015 at 01:29:51AM +0100, Uwe Stöhr wrote:
> Am 26.10.2015 um 22:42 schrieb Scott Kostyshak:
>
> - There are 2 sorts of layout issues that could violate the rule:
> 1. Layouts for journals: We often had the discussion about this and my own
> experience is that one MUST follow the l
On Mon, Oct 26, 2015 at 09:16:03PM +0100, Georg Baum wrote:
> Uwe Stöhr wrote:
>
> > Am 26.10.2015 um 06:31 schrieb Scott Kostyshak:
> >
> >>> I think it is safe enough to support 2 years old features and would
> >>> therefore like to put it in.
> >>
> >> Do we have any policy on this? What have
On Wed, Oct 28, 2015 at 09:19:14AM +0100, Kornel Benko wrote:
> Am Mittwoch, 28. Oktober 2015 um 02:34:54, schrieb Uwe Stöhr
>
> > Am 27.10.2015 um 08:09 schrieb Vincent van Ravesteijn:
> >
> > > So, to conclude, you should be able to run the test using:
> > >
> > > "ctest -R moderncv -C debug"
On Tue, Oct 27, 2015 at 08:47:41PM +0100, Georg Baum wrote:
> In case there was any misunderstanding: I am pretty sure that everybody
> agrees that the autotests (export tests, keytest etc) are not in a state
> that we can expect anybody to run them frequently.
Agreed. These tests are useful, f
Am Mittwoch, 28. Oktober 2015 um 02:34:54, schrieb Uwe Stöhr
> Am 27.10.2015 um 08:09 schrieb Vincent van Ravesteijn:
>
> > So, to conclude, you should be able to run the test using:
> >
> > "ctest -R moderncv -C debug" or "ctest -R moderncv -C release"
>
> many thanks Vinncent and Kornel!
>
>
Am 27.10.2015 um 20:32 schrieb Georg Baum:
I just sent the complete patch. Could you please apply it and test. I am
pretty sure it passes all tests but since i cannot perform them on my
own...
I tested it, and the tests pass.
Many thanks. I put it now in.
This does unfortunately not say mu
Am 27.10.2015 um 08:09 schrieb Vincent van Ravesteijn:
So, to conclude, you should be able to run the test using:
"ctest -R moderncv -C debug" or "ctest -R moderncv -C release"
many thanks Vinncent and Kornel!
This does now work for me:
- I added
-DLYX_ENABLE_EXPORT_TESTS=ON
to my build
Vincent van Ravesteijn wrote:
> On Tue, Oct 27, 2015 at 12:56 AM, Uwe Stöhr wrote:
>> Am 26.10.2015 um 16:51 schrieb Stephan Witt:
>
If things are that easy why can't they be documented? That is why we
have the Development.lyx file, no? There ctest is not mentioned.
It will be mention
Uwe Stöhr wrote:
> I just sent the complete patch. Could you please apply it and test. I am
> pretty sure it passes all tests but since i cannot perform them on my
> own...
I tested it, and the tests pass. This does unfortunately not say much,
because we do not have any tex2lyx test that uses th
>
> The same is with updating the tex2lyx reference files. I asked on the list
> but got not reply how I can do this:
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg189509.html
>
Yes, sorry that it took me a few days to take up the issue. The others
probably have a hard time debugging wh
Am Montag, 26. Oktober 2015 um 21:28:41, schrieb Richard Heck
> On 10/26/2015 05:42 PM, Scott Kostyshak wrote:
> > On Mon, Oct 26, 2015 at 01:56:48PM -0400, Richard Heck wrote:
> >> It might be worth renaming the old layout to moderncv-14.layout or
> >> something, in case people don't have the new
Am Dienstag, 27. Oktober 2015 um 00:56:39, schrieb Uwe Stöhr
> Am 26.10.2015 um 16:51 schrieb Stephan Witt:
>
> > You missed the "Change to the build-directory." part of Kornels advice.
> >
> > I think "D:\LyXGit\Master\lib\examples" isn't your build directory or at
> > least it shouldn't be so.
Scott Kostyshak wrote:
> What Uwe suggests seems reasonable to me at first thought for the rule:
> for a major release, we can have our layouts depend on the previous
> version of TeX Live. Currently there is TeX Live 2015 so anything that
> is supported in TeX Live 2014 we can depend on starting f
Am 27.10.2015 um 00:56 schrieb Uwe Stöhr :
> Am 26.10.2015 um 16:51 schrieb Stephan Witt:
>
>> You missed the "Change to the build-directory." part of Kornels advice.
>>
>> I think "D:\LyXGit\Master\lib\examples" isn't your build directory or at
>> least it shouldn't be so.
>
> Thanks for this
On Tue, Oct 27, 2015 at 12:56 AM, Uwe Stöhr wrote:
> Am 26.10.2015 um 16:51 schrieb Stephan Witt:
>
>> You missed the "Change to the build-directory." part of Kornels advice.
>>
>> I think "D:\LyXGit\Master\lib\examples" isn't your build directory or at
>> least it shouldn't be so.
>
>
> Thanks fo
On 10/26/2015 07:42 PM, Uwe Stöhr wrote:
Am 26.10.2015 um 03:50 schrieb Uwe Stöhr:
The attached patch adds support for the modernCV features introduced by
version 1.5 from April 2013.
Attached is not the complete patch including lyx2lyx and I hope it
addresses the tex2lyx tests as well.
If
On 10/26/2015 05:42 PM, Scott Kostyshak wrote:
On Mon, Oct 26, 2015 at 01:56:48PM -0400, Richard Heck wrote:
It might be worth renaming the old layout to moderncv-14.layout or
something, in case people don't have the new version.
This seems like a good idea to me. And then we could expire the o
Am 26.10.2015 um 22:42 schrieb Scott Kostyshak:
I see. It would be nice to have a rule so we don't have to have the same
discussion multiple times. We could add such a rule to Development.lyx.
Very good!
Today I searched the mailing list about this topic but I am only good on
searching, not o
Am 26.10.2015 um 16:51 schrieb Stephan Witt:
You missed the "Change to the build-directory." part of Kornels advice.
I think "D:\LyXGit\Master\lib\examples" isn't your build directory or at least
it shouldn't be so.
Thanks for this pointer. This works somehow but I still don't see if a
test
Am 26.10.2015 um 03:50 schrieb Uwe Stöhr:
The attached patch adds support for the modernCV features introduced by
version 1.5 from April 2013.
Attached is not the complete patch including lyx2lyx and I hope it
addresses the tex2lyx tests as well.
If nobody sees a problem with this, I would
On Mon, Oct 26, 2015 at 01:56:48PM -0400, Richard Heck wrote:
> On 10/26/2015 01:31 AM, Scott Kostyshak wrote:
> >On Mon, Oct 26, 2015 at 03:50:43AM +0100, Uwe Stöhr wrote:
> >>The attached patch adds support for the modernCV features introduced by
> >>version 1.5 from April 2013.
> >>
> >>I think
Uwe Stöhr wrote:
> Am 26.10.2015 um 06:31 schrieb Scott Kostyshak:
>
>>> I think it is safe enough to support 2 years old features and would
>>> therefore like to put it in.
>>
>> Do we have any policy on this? What have we done in the past?
>
> No strict one, but the feature should be at least
On 10/26/2015 01:31 AM, Scott Kostyshak wrote:
On Mon, Oct 26, 2015 at 03:50:43AM +0100, Uwe Stöhr wrote:
The attached patch adds support for the modernCV features introduced by
version 1.5 from April 2013.
I think it is safe enough to support 2 years old features and would
therefore like to pu
Am 26.10.2015 um 15:52 schrieb Uwe Stöhr :
> Am 26.10.2015 um 14:46 schrieb Vincent van Ravesteijn:
>
>>> I cannot find a command ctest to execute. How can or should I execute it?
>>
>> We have explained you this more than 2.5 years ago (see the link below).
>
> Sorry but no, you did not. The c
Am 26.10.2015 um 14:46 schrieb Vincent van Ravesteijn:
I cannot find a command ctest to execute. How can or should I execute it?
We have explained you this more than 2.5 years ago (see the link below).
Sorry but no, you did not. The cited mail does not explain how th tests
are run. Of cours
Op 26 okt. 2015 14:10 schreef "Uwe Stöhr" :
>
> Am 26.10.2015 um 06:31 schrieb Scott Kostyshak:
>
>>> I think it is safe enough to support 2 years old features and would
>>> therefore like to put it in.
>>
>>
>> Do we have any policy on this? What have we done in the past?
>
>
> No strict one, but
Am 26.10.2015 um 06:31 schrieb Scott Kostyshak:
I think it is safe enough to support 2 years old features and would
therefore like to put it in.
Do we have any policy on this? What have we done in the past?
No strict one, but the feature should be at least in the current and
previous TeXLiv
On Mon, Oct 26, 2015 at 03:50:43AM +0100, Uwe Stöhr wrote:
> The attached patch adds support for the modernCV features introduced by
> version 1.5 from April 2013.
>
> I think it is safe enough to support 2 years old features and would
> therefore like to put it in.
Do we have any policy on this?
The attached patch adds support for the modernCV features introduced by
version 1.5 from April 2013.
I think it is safe enough to support 2 years old features and would
therefore like to put it in.
Since a style is added, this would be a simple fileformat change.
OK to go on?
regards Uwe
di
46 matches
Mail list logo
