LyX 2.4.0dev Testing Release

Richard Kimberly Heck rikiheck at lyx.org
Sun Oct 25 19:55:32 UTC 2020


On 10/25/20 3:15 PM, Scott Kostyshak wrote:
> On Sun, Oct 25, 2020 at 07:59:55PM +0100, Kornel Benko wrote:
>> Am Sun, 25 Oct 2020 14:43:44 -0400
>> schrieb Richard Kimberly Heck <rikiheck at lyx.org>:
>>
>>> On 10/25/20 1:57 PM, Scott Kostyshak wrote:
>>>> On Sun, Oct 25, 2020 at 06:53:34PM +0100, Kornel Benko wrote:  
>>>>> Am Sun, 25 Oct 2020 13:48:15 -0400
>>>>> schrieb Scott Kostyshak <skostysh at lyx.org>:
>>>>>  
>>>>>> On Sun, Oct 25, 2020 at 04:55:52PM +0100, Kornel Benko wrote:  
>>>>>>> Am Sun, 25 Oct 2020 11:42:26 -0400
>>>>>>> schrieb Richard Kimberly Heck <rikiheck at lyx.org>:
>>>>>>>      
>>>>>>>>> Committed at 2dbf3515.
>>>>>>>>>
>>>>>>>>> Is there more?  
>>>>>>>> Should I try rebuilding?
>>>>>>>>
>>>>>>>> Is there a cmake way to generate the tarballs? I use 'make dist' from
>>>>>>>> autotools.
>>>>>>>>
>>>>>>>> Speaking of which, 'make lyxdist' used to work but doesn't now.
>>>>>>>>
>>>>>>>> Riki  
>>>>>>> If you do
>>>>>>>   $ make help
>>>>>>> in the build dir, you should get all possible targets.
>>>>>>> Among them
>>>>>>>   $ make package_source
>>>>>>> should create LyX-2.4.tar.gz and LyX-2.4.tar.xz  
>>>>>> Not sure if necessary, but in "cmake" call, you might need to set
>>>>>>
>>>>>>    -DLYX_CPACK=ON -DCPACK_SOURCE_TGZ:BOOL=ON
>>>>>>
>>>>>> Note that you can also create a .rpm. Not sure what your setup is, but
>>>>>> Kornel and I find it useful to use .debs (easy to install and remove).
>>>>>> To have "make package" create a .rpm, in "cmake" call do the following:
>>>>>>
>>>>>>    -DLYX_CPACK=ON -DCPACK_BINARY_RPM:BOOL=ON
>>>>>>
>>>>>> Scott  
>>>>> Yes, and the target is 'package', e.g.
>>>>>    $ make package  
>>>> Good point. To be clear (to Riki), "make package" will make CPack's
>>>> binary packages, which in the above example is the RPM. But for the
>>>> source tar.gz file, you still do "make package_source" as Kornel
>>>> mentioned earlier.  
>>> OK, thanks. I'll try this at some point.
>>>
>>> For my own use, I tend just to 'make install' to /usr/local/ and 
>>> over-write it as necessary. Is there reason to do it otherwise?
>>>
>>> Riki
>>>
>>>
>> Yes, it is. The next 'make install' does not remove old installed files.
>> For instance you move a file into different directory, or rename a file or delete in the
>> source.
>> Installing with the help of package manager is consistent.
> I like it for a few reasons:
>
> - I like having the package manager take care of it since that's what
>   they do best.
>
> - I think it takes care of things like opening .lyx files automatically
>   with the installed package. Not sure though, maybe I customized that a
>   while ago separately and that's why it works.
>
> - Although this doesn't come up in practice, for other situations if a
>   package depends on the "lyx" package, the package manager will not try
>   to install the package from the repository since it knows the
>   dependency is already satisfied.
>
> - I can save debs of old builds. I can also move them across machines.
>
> - I can send custom builds (e.g., to test something in particular) to
>   other Ubuntu users (I have done this and it works well).
>
> - For example, with very little extra work (e.g., no need to deal with
>   PPA), we can post a .deb for anyone who wants to test.
>
> That said, if something works with you, don't change it :)

Great, thanks.

How do I get a list of the cmake options available via -D? I assume I
could also create a deb file this way?

I have been meaning to automate regular testing builds...

Riki




More information about the lyx-devel mailing list