dev-lang/rust in the main Gentoo tree

[jauhien]

Let's discuss the future of Rust in Gentoo here.

[jauhien]

So far I've added 0.11.0 version to the tree and will add 9999 in a while. I'd ask all the interested to review it and give me a feedback, also I'd ask @Heather to co-maintain this package in case if @Heather wants.

Current issues I'd like to solve:

• unbundle of llvm for 9999 version, that's possible only for 9999 version as we need llvm-9999, also there is a problem with extern llvm still (see Add a USE flag to use system-wide LLVM #19 and Build with extern llvm fails rust-lang/rust#14729)
• unbundle other bundled stuff, basically every separate project used in rust compiler should have its own ebuild
• create/import ebuilds for rust-related stuff (begin with cargo), may be we'll need dev-rust category, but we need enough packages in it, so it's a good idea to add a bunch of such packages to overlay first, test them, then import them into the tree toghether with adding of a new category

Any propositions/ideas?

[jauhien]

And yes, deal with QA issues. )

[jauhien]

Live version added:

31 Jul 2014; Jauhien Piatlicki jauhien@gentoo.org
+files/rust-0.12.0-no-ldconfig.patch, +rust-9999.ebuild:
add live version, thanks to Heather Cynede for patch

[cnd]

@jauhien first of all thank you for coming here ( to my comfortable zone >_< )

• I will be glad to co-maintain rust package on gentoo-x86
• Also granting you push access to this overlay.
• patch was written by @omasanori also he has made major of work here 👍
• if this overlay will be large enough it should be moved to Gentoo organization, will have official status and we should think about motivating @omasanori to fill dev quiz.

[jauhien]

@omasanori, sorry, I'd not seen that you are the author, thanks for you work. )

@Heather, I'd like to have this overlay as a kind of experimental playground for the rust-stuff, so things are added first here, are discussed, then go to the tree. In order to have this, I'd ask you to review already added things, discuss them here and fix if there is a need for fix. Then back import them into this overlay.

Also a general discussion about what we need for good rust support in Gentoo is welcome I think. )

[jauhien]

@Heather so add yourself as maintainer in metadata. )

[omasanori]

unbundling of llvm for 9999 version, it's possible only for 9999 version as we need llvm-9999 for it, also there is a problem with extern llvm still

We have to require +multitarget on llvm until we get a better solution. Anyway we should ask LLVM guys in core dev whether the upstream LLVM can be used with current rustc.

unbundle other bundled stuff, basically every separate project used in rust compiler should have its own ebuild

Indeed but some of them might include patches not included in upstream yet.

it's a good idea to add a bunch of such packages to overlay first, test them, then import them into the tree toghether with adding of a new category

👍 Note that Cargo is fairly unstable so it must be too early to import for now. (see recent commit log of this overlay)

Also, I think all dev-lang/rust ebuilds should be replaced with @jauhien's ones because each ones have incompatible USE flags, dependencies, etc.

[jauhien]

Anyway we should ask LLVM guys in core dev whether the upstream LLVM can be used with current rustc.

As far as I remember they wanted to switch to the upstream. And all the patches are already in the upstream's latest version of llvm.

[omasanori]

@jauhien Yes, we did. However, I'm unsure whether we keep rust-lang/llvm without no in-house patches.

[jauhien]

If everybody is ok, I'll create different thematic issues to track what do we need. The first one will be about cargo. Please, comment in appropriate issue, so it would be easy to follow discussion.

[jauhien]

All live ebuilds were removed from the tree. From now the latest live Rust will be available only from this overlay. I will add versioned ebuilds to the tree along with coming of new versions and their stabilization.

[cnd]

@jauhien sounds good
Is there something else to keep this meta issue open?

[jauhien]

@Heather: probably no, any specific thing can be addressed by separate issue. Closing this.