Re: [update] productivity/timewarrior to 1.7.1

2024-03-23 Thread Stuart Henderson
On 2024/03/20 09:39, Nils Reuße wrote: > This update brings time warrior to the latest 1.7.1. It builds and runs fine > in my arm64-VM. : -MODPY_VERSION = ${MODPY_DEFAULT_VERSION_2} \o/ > Maybe someone knows a better way how to handle this, comments are very > welcome :) this was enough:

[update] productivity/timewarrior to 1.7.1

2024-03-20 Thread Nils Reuße
Hi, This update brings time warrior to the latest 1.7.1. It builds and runs fine in my arm64-VM. Tests are now enabled, but in a somewhat hacky way, because my cmake-skills are nonexistent. When running `make test` outside the ports directory, cmake does the right thing, but using the ports

Re: update productivity/timewarrior

2023-08-17 Thread Ashlen
On Thu, 3 Aug 2023 22:55 +0100, Stuart Henderson wrote: > On 2023/08/03 12:24, Ashlen wrote: > > On Thu, 3 Aug 2023 17:37 +0100, Stuart Henderson wrote: > > > you can get tests to run with these (and this also needs > > > SEPARATE_BUILD = No otherwise when it builds the .t binaries, it puts > >

Re: update productivity/timewarrior

2023-08-03 Thread Stuart Henderson
On 2023/08/03 12:24, Ashlen wrote: > On Thu, 3 Aug 2023 17:37 +0100, Stuart Henderson wrote: > > you can get tests to run with these (and this also needs > > SEPARATE_BUILD = No otherwise when it builds the .t binaries, it puts > > them in the build dir, and there's nothing setup to replace the

Re: update productivity/timewarrior

2023-08-03 Thread Ashlen
On Thu, 3 Aug 2023 17:37 +0100, Stuart Henderson wrote: > you can get tests to run with these (and this also needs > SEPARATE_BUILD = No otherwise when it builds the .t binaries, it puts > them in the build dir, and there's nothing setup to replace the MacOS > binaries present in the test dir in

Re: update productivity/timewarrior

2023-08-03 Thread Stuart Henderson
you can get tests to run with these (and this also needs SEPARATE_BUILD = No otherwise when it builds the .t binaries, it puts them in the build dir, and there's nothing setup to replace the MacOS binaries present in the test dir in the tar). TEST_DEPENDS = ${MODPY_RUN_DEPENDS} USE_NINJA

update productivity/timewarrior

2023-08-02 Thread Ashlen
Updates productivity/timewarrior from 1.1.1 to 1.5.0. https://github.com/GothenburgBitFactory/timewarrior/releases/tag/v1.5.0 https://github.com/GothenburgBitFactory/timewarrior/compare/v1.1.1...v1.5.0 I looked to see if NO_TESTING could be removed, but didn't see an obvious way to get tests to

Re: update productivity/timewarrior. Was [Re: update productivity/taskwarrior to 2.6.1]

2021-11-18 Thread Stuart Henderson
On 2021/11/18 02:49, Erling Westenvik wrote: > On Wed, Nov 17, 2021 at 05:35:08PM +0100, Paco Esteban wrote: > > On Sun, 14 Nov 2021, Erling Westenvik wrote: > > > > > Thanks for caring about taskwarrior. Any chance that you can update > > > timewarrior too? Since the two are kind of siblings

Re: update productivity/timewarrior. Was [Re: update productivity/taskwarrior to 2.6.1]

2021-11-17 Thread Erling Westenvik
On Wed, Nov 17, 2021 at 05:35:08PM +0100, Paco Esteban wrote: > On Sun, 14 Nov 2021, Erling Westenvik wrote: > > > Thanks for caring about taskwarrior. Any chance that you can update > > timewarrior too? Since the two are kind of siblings from the same > > developers I mean? Our 1.1.1p0 lags

update productivity/timewarrior. Was [Re: update productivity/taskwarrior to 2.6.1]

2021-11-17 Thread Paco Esteban
On Sun, 14 Nov 2021, Erling Westenvik wrote: > Thanks for caring about taskwarrior. Any chance that you can update > timewarrior too? Since the two are kind of siblings from the same > developers I mean? Our 1.1.1p0 lags awfully behind the official 1.4.3. I don't use timewarrior at all, so I