From: Peter Volkov <pva@gentoo.org>
To: Hans de Graaff <graaff@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog package.mask
Date: Tue, 16 Nov 2010 11:13:11 +0300 [thread overview]
Message-ID: <1289895191.10361.12.camel@tablet> (raw)
In-Reply-To: <1289890421.4297.11.camel@localhost>
eiВ Втр, 16/11/2010 в 07:53 +0100, Hans de Graaff пишет:
> On Tue, 2010-11-16 at 06:40 +0000, Peter Volkov (pva) wrote:
> >
> > +# Peter Volkov <pva@gentoo.org> (16 Nov 2010)
> > +# Last rites: dev-python/py-rrdtool #345701
> > +# Old python bindins that currently are included into net-analyzer/rrdtool
> > +# Removal on 16 Dec 2010
> > +dev-python/py-rrdtool
>
> I have a similar todo item on my list for the standalone ruby bindings,
> but I have not masked them yet because rrdtool 1.0.50 doesn't include
> them and is still in the tree. I'm not sure when the python bindings got
> incorporated into rrdtool, but I'm guessing it might be similar.
> Any plans to remove rrdtool-1.0.50 from the tree? Or should I just go
> ahead and remove the ruby bindings anyway?
rrdtool-1.0 is used by SFlowtool and last time I've tried it worked so I
don't see any reason to drop rrdtool-1.0.50 from the tree. As for
bindings, py-rrdtool have known problems and thus I've decided to drop
it. Probably it's good idea to do the same for ruby bindings as rrdtool
ChangeLog suggests that some problems were fixed there too.
If users need bindings they better use recent rrdtool and bundled
bindings, rrdtool-1.0.x for sflowtool only.
--
Peter.
next parent reply other threads:[~2010-11-16 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101116064059.3E60F20051@flycatcher.gentoo.org>
[not found] ` <1289890421.4297.11.camel@localhost>
2010-11-16 8:13 ` Peter Volkov [this message]
[not found] <20130813001402.E87AD2171C@flycatcher.gentoo.org>
2013-08-13 2:29 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog package.mask Samuli Suominen
2013-08-13 11:37 ` Alexis Ballier
2013-08-13 12:13 ` Alexis Ballier
[not found] <20130419091632.D01152171D@flycatcher.gentoo.org>
2013-04-19 13:30 ` Alexis Ballier
2013-04-20 17:28 ` Jeroen Roovers
2013-04-21 12:53 ` Ben de Groot
2013-04-21 14:11 ` Denis Dupeyron
2013-04-21 14:23 ` Rich Freeman
2013-04-21 14:39 ` Denis Dupeyron
2013-04-21 14:38 ` Chí-Thanh Christopher Nguyễn
2013-04-21 14:50 ` Denis Dupeyron
2013-04-21 15:07 ` Chí-Thanh Christopher Nguyễn
2013-04-21 15:17 ` Alexis Ballier
2013-04-22 11:43 ` Ben de Groot
2013-04-22 17:13 ` Michał Górny
2013-04-23 16:16 ` Ben de Groot
2013-04-22 12:07 ` Ben de Groot
2013-04-21 14:59 ` Alexis Ballier
2013-04-22 11:56 ` Ben de Groot
2013-04-22 14:00 ` Alexis Ballier
2013-04-23 3:58 ` Ryan Hill
2013-04-23 16:24 ` Ben de Groot
2013-04-24 10:59 ` Duncan
2013-04-30 2:06 ` Ryan Hill
[not found] <E1L80EJ-0006xU-0U@stork.gentoo.org>
2008-12-03 21:31 ` Robin H. Johnson
2008-12-04 3:56 ` Alec Warner
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=1289895191.10361.12.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=graaff@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