| 1 |
On 09/05/2015 02:21 PM, Jauhien Piatlicki wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I have plans to split ?/cargo-bin [1] package from the dev-lang/rust-bin |
| 5 |
> one. We have already dev-rust/cargo package in the rust overlay[2]. |
| 6 |
> |
| 7 |
> It would be logical to have dev-rust/cargo-bin package then. But there |
| 8 |
> is a problem: it will be the only package in this category in the tree |
| 9 |
> and it is not welcome to have categories with small number of packages. |
| 10 |
> Other rust stuff will appear, but later (with no estimate), as a number |
| 11 |
> of problems with packaging source rust packages should be solved before |
| 12 |
> (afaik upstream also has plans to improve rust packaging). The same |
| 13 |
> about moving source cargo to the tree. |
| 14 |
> |
| 15 |
> So what is better, create dev-util/cargo-bin package and later, when |
| 16 |
> rust infrastructure grows, move it to the dev-rust category or create |
| 17 |
> new category now? |
| 18 |
> |
| 19 |
> [1] https://crates.io/ |
| 20 |
> [2] https://github.com/Heather/gentoo-rust |
| 21 |
> |
| 22 |
> -- |
| 23 |
> Jauhien |
| 24 |
> |
| 25 |
|
| 26 |
I think cargo should probably go in dev-util with other rust libraries |
| 27 |
and programs going into dev-rust as needed, but that's just me :D |
| 28 |
|
| 29 |
-- |
| 30 |
Matthew Thode (prometheanfire) |
Archives