Date: Sat, 5 Jul 2008 10:20:43 -0300 From: JoaoBR <joao@matik.com.br> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: cvs-ports@freebsd.org, bg1tpt@gmail.com, ports-committers@freebsd.org Subject: Re: rrdtool waked Message-ID: <200807051020.43845.joao@matik.com.br> In-Reply-To: <20080705124246.GA79996@eos.sc1.parodius.com> References: <200807050919.m659JG60084247@repoman.freebsd.org> <200807050836.54442.joao@matik.com.br> <20080705124246.GA79996@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 05 July 2008 09:42:46 Jeremy Chadwick wrote: > On Sat, Jul 05, 2008 at 08:36:54AM -0300, JoaoBR wrote: > > a week ago portupgrade fucked rrdtool up and now it got worse > > why rrdtool is installing all this new and unecessessary dependencies? > > X11 font stuff, including python with it sub-ports even if only the cgi > > module is selected, what is next? kpresenter dependency to make better > > artwork on a server? > > and there is'nt the smallest advice in UPDATING ... > > that was really not so very cool, you could have made an option for this > > extra stuff > > It's not extra. rrdtool now requires Cairo and Pango, which require > tons of X fonts and other things. They are *mandatory* for rrdtool to > function, as can be confirmed here: > > http://oss.oetiker.ch/rrdtool-trac/wiki/RRDtool13 > > The number of dependencies in the port has grown from something like 12 > to 35. There's nothing we can really do about it. It's not the fault > of the port maintainer -- it's the fault of rrdtool. > hum, sorry then, I never ever looked again there because it ever worked - l= ame=20 excuse I know and thank's for clarification even so a little hello in UPDATING would not be so bad > <opinion> > rrdtool is worth *avoiding* at all costs. The only reason it's used > so much is because it's the only choice available in the open-source > world. (Well actually there's RTG, but it's in a complete state of > disarray, and to get any decent features you have to use the version > in CVS rather than the "stable" build...) I'm still amazed that no one > has written an alternative. > > I've hated rrdtool since day one of using it. Yes, because all of > those cryptic command-line arguments for creating RRAs and DSes make so > much sense when reading them; because config files are just too hard. > Sure, those arguments work, but 6 months from now when you need to do > something with the database, you get to re-learn what all of that crap > means. :)=20 > > And don't even get me started on the "API" it claims to have. > > The rrdtool 1.3 upgrade is the "last straw" for me. We've pulled > anything that uses rrdtool off of our production systems; that means > no more symon/symux, cacti, or anything else. I would highly recommend > others do the same. > </opinion> > > Bottom line: send all flames to Tobias Oetiker. well, he would say "send patches" I guess :)=20 even if you are right, it is the only one for graphing multi data and it wo= rks=20 and quiet well so why make another? thank's =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807051020.43845.joao>