> On May 21, 2019, at 6:08 AM, Derek Atkins wrote:
>
> John Ralls writes:
>
>>> On May 20, 2019, at 6:02 AM, Derek Atkins wrote:
>>>
>>> Does the tarfile not create a tree gnucash_XX (where XX is the
>>> git hash of the tarball)?
>>>
>>> I guess there is no way to disable this "fe
John Ralls writes:
>> On May 20, 2019, at 6:02 AM, Derek Atkins wrote:
>>
>> Does the tarfile not create a tree gnucash_XX (where XX is the
>> git hash of the tarball)?
>>
>> I guess there is no way to disable this "feature" of github?
>
> Nope. It just creates a zip file "gnucash-maint
> On May 20, 2019, at 6:02 AM, Derek Atkins wrote:
>
> Geert Janssens writes:
>
>>> Another alternative is just print "GITHUB RELEASE XXX" and grab XXX from
>>> the top-level directory name?
>>
>> The top-level directory name can be anything and not related to git or github
>> at all. It de
Geert Janssens writes:
>> Another alternative is just print "GITHUB RELEASE XXX" and grab XXX from
>> the top-level directory name?
>
> The top-level directory name can be anything and not related to git or github
> at all. It depends on where a user extracts the zip file.
Does the tarfile not c
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
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
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
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
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
> 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
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
> 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 question is when to introduce this ? Would you do it for the next
> stable
Op woensdag 15 mei 2019 15:43:43 CEST schreef John Ralls:
> OK, that all sounds reasonable.
>
> Regards,
> John Ralls
Glad you agree.
Remaining question is when to introduce this ? Would you do it for the next
stable release or on master ? I'm inclined to go for the latter as not to trip
up to
13 matches
Mail list logo
