public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, multilib@gentoo.org
Subject: [gentoo-dev] Re: The gx86-multilib project needs your help! (+ roadmap reminder)
Date: Tue, 13 May 2014 21:19:22 +0200	[thread overview]
Message-ID: <1400008762.13920.6.camel@belkin5> (raw)
In-Reply-To: <20140511205642.5bf0aa5c@pomiot.lan>

El dom, 11-05-2014 a las 20:56 +0200, Michał Górny escribió:
[...]
> 4. whenever possible, depend on the specific subslot that is known to
> provide SONAME equal to the required by your package, e.g. for
> libgcrypt.so.20 you depend on libgcrypt:0/20,
[...]

Why is this needed? Thanks for the explanation :)



  reply	other threads:[~2014-05-13 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 18:56 [gentoo-dev] The gx86-multilib project needs your help! (+ roadmap reminder) Michał Górny
2014-05-13 19:19 ` Pacho Ramos [this message]
2014-05-13 19:23   ` [gentoo-dev] " Ian Stakenvicius
2014-05-15  7:23     ` Pacho Ramos
2014-05-14 10:13 ` [gentoo-dev] " Ulrich Mueller

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=1400008762.13920.6.camel@belkin5 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    --cc=multilib@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