From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: How to handle dependencies on protocol headers?
Date: Fri, 16 Sep 2011 00:42:57 -0400 [thread overview]
Message-ID: <CAEdQ38G6WxxLZJnkQvrMqT8xhhswEm3BjZjDbKAafyB131AXBQ@mail.gmail.com> (raw)
In-Reply-To: <CAEdQ38EpZVFZktC3LnT06YbXqC5iErmw6RhifEyAV0D9ftusSw@mail.gmail.com>
On Fri, Sep 16, 2011 at 12:32 AM, Matt Turner <mattst88@gentoo.org> wrote:
> Often packages depending on X11 libraries will also have to specify
> the X11 libraries' proto packages in DEPEND. This is because the X11
> library itself #includes files provided by the proto package. It's not
> really that the X11 library depends on this at run-time, so the
> protocol packages aren't specified in the RDEPEND of the libraries.
>
> This is documented in a number of bug reports (see 379545), and it
> seems that the decision is between
> - add proto package to dependency list of packages using X11 libs
> - add proto package to rdepend list of the relevant library itself
>
> The first is more correct, I think, but it's also much more annoying.
> Mesa winds up having x11-proto/inputproto in DEPEND for some long
> forgotten reason, for instance.
>
> The second option is much simpler and less error prone, but removes
> the ability to depclean the proto packages.
>
> It seems that some sort of DEPEND variable that means "I only need
> this when other packages are building against me" would be useful.
> Thoughts?
>
> Matt
Another similar situation:
https://bugs.gentoo.org/show_bug.cgi?id=342393
next prev parent reply other threads:[~2011-09-16 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 4:32 [gentoo-dev] How to handle dependencies on protocol headers? Matt Turner
2011-09-16 4:36 ` Alec Warner
2011-09-16 4:47 ` Matt Turner
2011-09-16 4:42 ` Matt Turner [this message]
2011-09-16 4:49 ` [gentoo-dev] " Zac Medico
2011-09-16 5:00 ` Alexander Bersenev
2011-09-16 5:24 ` Matt Turner
2011-09-16 6:25 ` [gentoo-dev] " Ciaran McCreesh
2011-09-16 7:54 ` Michał Górny
2011-09-16 8:08 ` Ciaran McCreesh
2011-09-16 9:15 ` Brian Harring
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=CAEdQ38G6WxxLZJnkQvrMqT8xhhswEm3BjZjDbKAafyB131AXBQ@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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