public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jauhien Piatlicki <jauhien@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] dev-rust category
Date: Sat, 5 Sep 2015 21:21:01 +0200	[thread overview]
Message-ID: <55EB409D.9090508@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Hi,

I have plans to split ?/cargo-bin [1] package from the dev-lang/rust-bin
one. We have already dev-rust/cargo package in the rust overlay[2].

It would be logical to have dev-rust/cargo-bin package then. But there
is a problem: it will be the only package in this category in the tree
and it is not welcome to have categories with small number of packages.
Other rust stuff will appear, but later (with no estimate), as a number
of problems with packaging source rust packages should be solved before
(afaik upstream also has plans to improve rust packaging). The same
about moving source cargo to the tree.

So what is better, create dev-util/cargo-bin package and later, when
rust infrastructure grows, move it to the dev-rust category or create
new category now?

[1] https://crates.io/
[2] https://github.com/Heather/gentoo-rust

--
Jauhien


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-09-05 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05 19:21 Jauhien Piatlicki [this message]
2015-09-05 20:04 ` [gentoo-dev] [RFC] dev-rust category Matthew Thode
2015-09-05 21:23   ` Daniel Campbell
2015-09-06 21:00     ` Jauhien Piatlicki
2015-09-07  5:28       ` Daniel Campbell
2015-09-07 12:56         ` Jauhien Piatlicki
2015-09-07 15:47           ` Daniel Campbell

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=55EB409D.9090508@gentoo.org \
    --to=jauhien@gentoo.org \
    --cc=gentoo-dev@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