From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25509] Break a cyclic dependency by core packages
Date: Sun, 01 Mar 2020 17:53:00 -0000 [thread overview]
Message-ID: <bug-25509-10460-VYIswlOUhI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25509-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25509
--- Comment #6 from Frank Ch. Eigler <fche at redhat dot com> ---
(In reply to Eli Schwartz from comment #5)
> > # Look for libmicrohttpd, libcurl, libarchive, sqlite for debuginfo server
> > # minimum versions as per rhel7. Single --enable-* option arranges to build
> > # both client and server.
>
> Maybe this should not be the case? If libdebuginfod was enabled on its own
> as long as libcurl is available, this would make things a lot simpler. At
> least for Arch Linux, curl is part of the base system while libmicrohttpd is
> not.
This part wouldn't affect the suse/fedora folks, because one would already
place the debuginfod server into a separate subpackage, so its prereqs don't
affect the buildroot.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-01 17:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 15:13 [Bug debuginfod/25509] New: " marxin.liska at gmail dot com
2020-02-05 15:16 ` [Bug debuginfod/25509] " marxin.liska at gmail dot com
2020-02-06 11:35 ` mark at klomp dot org
2020-02-06 12:53 ` fche at redhat dot com
2020-02-06 13:34 ` marxin.liska at gmail dot com
2020-03-01 17:37 ` eschwartz at archlinux dot org
2020-03-01 17:53 ` fche at redhat dot com [this message]
2020-06-07 20:36 ` mark at klomp dot org
2020-06-08 7:33 ` mliska at suse dot cz
2020-06-19 17:56 ` mark at klomp dot org
2020-06-19 18:03 ` fche at redhat dot com
2020-06-24 21:14 ` mark at klomp dot org
2020-06-24 21:18 ` mark at klomp dot org
2020-06-24 23:55 ` eschwartz at archlinux dot org
2020-06-25 0:14 ` fche at redhat dot com
2020-06-25 0:22 ` eschwartz at archlinux dot org
2020-06-25 0:23 ` fche at redhat dot com
2020-06-25 8:51 ` mark at klomp dot org
2020-06-25 9:06 ` mliska at suse dot cz
2020-07-03 21:24 ` eschwartz at archlinux dot org
2020-07-03 21:34 ` eschwartz at archlinux dot org
2020-07-03 23:34 ` mark at klomp dot org
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=bug-25509-10460-VYIswlOUhI@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/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.
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).