From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] [rust] Weekly report
Date: Sat, 12 May 2018 23:32:00 +0200 [thread overview]
Message-ID: <efd95e8e-cdec-26fc-3171-764d6f7e3724@gentoo.org> (raw)
In-Reply-To: <20180512180303.GA5933@nolla>
On 12/05/2018 20:03, gibix wrote:
> Hello!
>
> I spent the week to setting up the environment and keeping track
> discussions in the rust community, this is particularly important for the
> cargo-ebuild design. I made a presentation of the project at the local
> rust meetup.
>
> The full report with references to resources, commits and more can be found
> here:
> https://gibix.github.io/2018/05/11/gsoc-weekly-report.html
>
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.
lu
next prev parent reply other threads:[~2018-05-12 21:32 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 [this message]
2018-05-13 16:04 ` bic
-- 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=efd95e8e-cdec-26fc-3171-764d6f7e3724@gentoo.org \
--to=lu_zero@gentoo.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