From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rng-tools
Date: Tue, 06 Mar 2012 11:32:08 +0100 [thread overview]
Message-ID: <4F55E7A8.9040803@gentoo.org> (raw)
In-Reply-To: <CA+czFiB1Q2f8r=_O0TN7BvMT7Q1T=7cYfQrDEO5Wx2i_Z-DRXw@mail.gmail.com>
Hello Michael,
On 03/03/2012 02:48 PM, Michael Mol wrote:
> The version of the rng-tools Debian package I'm using is
> '2-unofficial-mt.14-1~60squeeze1'. Are the -T and -R parameters unique
> to Debian, or is the Gentoo package simply out of date?
Yes, version 2-unofficial-mt.14* is a Debian fork. Quoting from its
README file:
rng-tools, unofficial Debian fork
=================================
NOTICE:
This is an unofficial version of rng-tools with a lot of added
functionality and bugs, for which I assume total blame. Don't bother
rng-tools upstream with problems you find in this version of
rng-tools.
rng-tools unofficial-mt is a living reminder to myself to not modify
upstream code without sending the changes upstream at every step.
Suddenly, you have a mass of changes too big to send upstream, and
yet you find yourself without the energy to break them into smallish
patches to submit upstream (i.e. to "unfork").
[..]
If you would rather use Debian's version in Gentoo, give
sys-apps/rng-tools-2_p14
a try, which I have just added to overlay betagarden:
# layman -a betagarden
# emerge =sys-apps/rng-tools-2_p14
If you would like to see features from Debian's fork in rng-tools 3.x
and beyond, please step up and help rng-tools' upstream integrate
Debian's changes.
Best,
Sebastian
next prev parent reply other threads:[~2012-03-06 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 13:48 [gentoo-user] rng-tools Michael Mol
2012-03-03 14:00 ` Alan McKinnon
2012-03-03 15:04 ` Pandu Poluan
2012-03-03 15:32 ` Alan McKinnon
2012-03-06 10:32 ` Sebastian Pipping [this message]
2012-04-13 1:14 ` Michael Mol
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=4F55E7A8.9040803@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-user@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