[gentoo-soc] [rust] Weekly report

[gentoo-soc] [rust] Weekly report

[gibix]

Hello!

Here the report of my second week:

https://gibix.github.io/2018/05/25/gsoc-week-2-report.html

I'm at the RustFest in paris and on Mo/Tu I will attend the Impl Days
trying to work with the rust community and discuss about my project.

Have a nice week

gbx

[gentoo-soc] [rust] Weekly report

[gibix]

Hello!

Happy to share with you the first report of the gsoc's coding period.

https://gibix.github.io/2018/05/20/gsoc-week-1-report.html

I collected my first impression about writing CLIs with rust and how to
deal with errors. The links are a good collections of starting point for
those who wants to get their hands dirty with the language.

Have a good week

gbx

[gentoo-soc] [rust] Weekly report

[gibix]

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

Have a nice weekend!

gbx

Re: [gentoo-soc] [rust] Weekly report

[Luca Barbato]

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

Re: [gentoo-soc] [rust] Weekly report

[bic]

> 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.