From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Taiju HIGASHI <higashi@taiju.info>
Cc: 53536@debbugs.gnu.org, me@tobias.gr, leo@famulari.name, marius@gnu.org
Subject: [bug#53536] [PATCH v2] gnu: Include poppler-data with poppler.
Date: Thu, 03 Feb 2022 07:54:10 +0100 [thread overview]
Message-ID: <d65c054e03d5be27ad93e81e979db2b3e1e2f595.camel@ist.tugraz.at> (raw)
In-Reply-To: <87mtj9jmnq.fsf@taiju.info>
Am Donnerstag, dem 03.02.2022 um 00:47 +0900 schrieb Taiju HIGASHI:
> > Assertion (2) is wrong here: gimp's configure.ac directly checks for
> > the existence of poppler-data. That makes it a direct dependency as
> > far as I'm concerned, even if they only ever use it through poppler.
>
> I did not convey the context correctly.
>
> I thought I was describing the behavior of the gimp package with the
> poppler-data dependency removed (= gimp,which indirectly depend on
> poppler-data).
> In that state, gimp will fail to build because pkg-config cannot detect
> poppler-data during the build process.
> Therefore, I left the poppler-data dependency in gimp.
>
> I'm really sorry for my poor explanation.
Again, w.r.t. your explanation I claim that gimp does not "indirectly"
depend on poppler-data, but directly. Voilà, le configure.ac [1].
[1]
https://gitlab.gnome.org/GNOME/gimp/-/blob/GIMP_2_10_30/configure.ac#L2023-L2024
next prev parent reply other threads:[~2022-02-03 7:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 23:59 [bug#53536] [PATCH 0/1] Add poppler-with-data Taiju HIGASHI
2022-01-26 0:20 ` [bug#53536] [PATCH 1/1] gnu: " Taiju HIGASHI
2022-01-26 7:37 ` [bug#53536] [PATCH 0/1] " Liliana Marie Prikler
2022-01-26 13:38 ` Taiju HIGASHI
2022-01-26 14:16 ` Liliana Marie Prikler
2022-01-27 0:55 ` Taiju HIGASHI
2022-01-26 13:42 ` Taiju HIGASHI
2022-02-02 3:48 ` [bug#53536] [PATCH v2] gnu: Include poppler-data with poppler Taiju HIGASHI
2022-02-02 7:27 ` Liliana Marie Prikler
2022-02-02 13:35 ` Taiju HIGASHI
2022-02-02 14:16 ` Liliana Marie Prikler
2022-02-02 15:47 ` Taiju HIGASHI
2022-02-03 6:54 ` Liliana Marie Prikler [this message]
2022-02-03 7:23 ` Taiju HIGASHI
2022-02-02 3:58 ` [bug#53536] [PATCH 0/1] Add poppler-with-data Taiju HIGASHI
2022-02-02 6:22 ` [bug#53536] [PATCH v2] gnu: Include poppler-data with poppler Taiju HIGASHI
2022-02-03 6:23 ` [bug#53536] [PATCH v3 1/2] gnu: poppler: Add poppler-data Taiju HIGASHI
2022-02-03 6:23 ` [bug#53536] [PATCH v3 2/2] gnu: pdf2djvu: Remove poppler-data Taiju HIGASHI
2022-02-03 6:28 ` Taiju HIGASHI
2022-02-06 0:00 ` bug#53536: [PATCH v3 1/2] gnu: poppler: Add poppler-data Liliana Marie Prikler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d65c054e03d5be27ad93e81e979db2b3e1e2f595.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=53536@debbugs.gnu.org \
--cc=higashi@taiju.info \
--cc=leo@famulari.name \
--cc=marius@gnu.org \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.