From: bic <bicno@autistici.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] [rust] Weekly report
Date: Sun, 13 May 2018 18:04:50 +0200 [thread overview]
Message-ID: <20180513160450.GB5933@nolla> (raw)
In-Reply-To: <efd95e8e-cdec-26fc-3171-764d6f7e3724@gentoo.org>
> You should explain better what you mean with dropping metadeps, I'm
> quite sure there isn't a better way to express pkg-config dependencies
> right now and I would not suggest to parse/process all crate build.rs to
> extract the same information from there.
From the cargo-ebuild point of view is necessary on the pkg-config metadata
exported as ebuild. This possibly with an easy way to to match feature with
use flags when are available.
next prev parent reply other threads:[~2018-05-13 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 18:03 [gentoo-soc] [rust] Weekly report gibix
2018-05-12 21:32 ` Luca Barbato
2018-05-13 16:04 ` bic [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-20 18:25 gibix
2018-05-27 10:53 gibix
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=20180513160450.GB5933@nolla \
--to=bicno@autistici.org \
--cc=gentoo-soc@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