Re: [GNC-dev] swig as permanent build requirement (was: Re: [GNC] UK VAT and "Making Tax Digital")

Op donderdag 16 mei 2019 16:05:56 CEST schreef John Ralls: > > On May 16, 2019, at 1:39 AM, Geert Janssens > > wrote:> > > Op donderdag 16 mei 2019 05:24:04 CEST schreef John Ralls: > OK, create a flag file that the dist target makes and isn't present > otherwise. My objective is to find a way to

Re: [GNC-dev] automated tech for setup of builds + HELLO

On 5/16/19 11:04 AM, Stephen M. Butler wrote: > On 5/15/19 9:01 AM, Dale Phurrough via gnucash-devel wrote: >> Thanks for everyone's feedback. I've released >> https://github.com/diablodale/gnucash-dev-docker a set of Docker containers >> and an example docker-compose to automate. >> I appreciate e

Re: [GNC-dev] verifying bug fixes - bug lifecycle - what happened to VERIFIED?

OK. Very few users set VERIFIED, but you may if you like. Most users aren't shy about reopening a bug if the expected fix doesn't work for them. Regards, John Ralls > On May 16, 2019, at 8:59 AM, Dale Phurrough via gnucash-devel > wrote: > > What is the de facto process, or if written, on th

Re: [GNC-dev] automated tech for setup of builds + HELLO

On 5/15/19 9:01 AM, Dale Phurrough via gnucash-devel wrote: > Thanks for everyone's feedback. I've released > https://github.com/diablodale/gnucash-dev-docker a set of Docker containers > and an example docker-compose to automate. > I appreciate everyone's feedback on these and my approach. These e

Re: [GNC-dev] swig as permanent build requirement

Op donderdag 16 mei 2019 17:08:25 CEST schreef Derek Atkins: > Geert Janssens writes: > > For starters despite our advice several people still prefer to build in > > source. It appears this notion of a separate build directory is not > > ingrained deeply into the development ecosystem. > > *I* li

Re: [GNC-dev] swig as permanent build requirement

Op donderdag 16 mei 2019 19:17:29 CEST schreef Stephen M. Butler: > On 5/16/19 8:08 AM, Derek Atkins wrote: > > Geert Janssens writes: > >> For starters despite our advice several people still prefer to build in > >> source. It appears this notion of a separate build directory is not > >> ingraine

Re: [GNC-dev] swig as permanent build requirement

On 5/16/19 8:08 AM, Derek Atkins wrote: > Geert Janssens writes: > >> For starters despite our advice several people still prefer to build in >> source. It appears this notion of a separate build directory is not >> ingrained >> deeply into the development ecosystem. > *I* like to build in sour

[GNC-dev] verifying bug fixes - bug lifecycle - what happened to VERIFIED?

What is the de facto process, or if written, on the transition from RESOLVED bug -> VERIFIED bug for the Gnucash project? My inquiry is due to a private conversation...bringing it broader. I checked and haven't yet found a gnucash doc on this. Personally, the bug lifecycle I'm most familiar has t

Re: [GNC-dev] swig as permanent build requirement

Geert Janssens writes: > For starters despite our advice several people still prefer to build in > source. It appears this notion of a separate build directory is not ingrained > deeply into the development ecosystem. *I* like to build in source! Or, more technically, I use lndir to create a

Re: [GNC-dev] swig as permanent build requirement (was: Re: [GNC] UK VAT and "Making Tax Digital")

> On May 16, 2019, at 1:39 AM, Geert Janssens > wrote: > > Op donderdag 16 mei 2019 05:24:04 CEST schreef John Ralls: >>> On May 15, 2019, at 7:49 AM, Geert Janssens >>> wrote:> >>> Op woensdag 15 mei 2019 15:43:43 CEST schreef John Ralls: OK, that all sounds reasonable. Reg

Re: [GNC-dev] swig as permanent build requirement (was: Re: [GNC] UK VAT and "Making Tax Digital")

Op donderdag 16 mei 2019 05:24:04 CEST schreef John Ralls: > > On May 15, 2019, at 7:49 AM, Geert Janssens > > wrote:> > > Op woensdag 15 mei 2019 15:43:43 CEST schreef John Ralls: > >> OK, that all sounds reasonable. > >> > >> Regards, > >> John Ralls > > > > Glad you agree. > > > > Remaining