From: Marius Bakke <mbakke@fastmail.com>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: leptonica: Update to 1.73.
Date: Tue, 27 Dec 2016 17:20:19 +0100 [thread overview]
Message-ID: <87r34twdh8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87fulbdbsk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
"Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com> writes:
>>
>>> You know what, Leptonica 1.74.0 has been released yesterday, so here's a
>>> new patch. :-D
>>>
>>> But yes, the source snippet / patch for the .pc file isn't necessary
>>> anymore for reasons not really clear to me. (The two libs still need to
>>> be propagated and Tesseract has to link against them; maybe Tesseract
>>> special-handles this and other dependents of Leptonica could still
>>> benefit from a patched .pc file, but so far we don't have any other
>>> dependents of Leptonica...)
>>>
>>> The config.h hack probably wasn't necessary anymore since 1.72; I had
>>> introduced it with 1.71 where the issue existed and it didn't get
>>> removed upon the 1.72 update.
>>>
>>> And all tests pass, without having to disable parallel tests either.
>>>
>>> The 1.74.0 tag on GitHub corresponds to a state in which ./configure
>>> doesn't exist; the autobuild script needs to be run.
>>>
>>> So here's the new patch.
>>
>> Thanks for the clarification and update, pushed!
>>
>> I completely forgot to mention the origin and argument changes in the
>> commit message as we usually do. Hopefully the next update can include
>> that too ;-)
>
> Thanks. :-)
>
> FYI I have push access so in the future you can just tell me to push it.
Oh, thanks for letting me know :-)
> I guess I can be more strict with the commit lines. Usually I assume
> that some changes to the rest of the recipe are implied in a version
> update...
I think it is useful to mention such changes in the commit message, so
that one can clearly see in the git log which commit introduced e.g. a
new phase, or new source URL, instead of having to dig through the full
diffs (or blame) to find it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2016-12-27 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 21:10 [PATCH] gnu: leptonica: Update to 1.73 "Taylan Ulrich Bayırlı/Kammer"
2016-12-24 14:17 ` Marius Bakke
2016-12-24 16:19 ` Taylan Ulrich Bayırlı/Kammer
2016-12-25 13:01 ` Marius Bakke
2016-12-25 19:54 ` Taylan Ulrich Bayırlı/Kammer
2016-12-27 16:20 ` Marius Bakke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r34twdh8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).