public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pva@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/cacti: ChangeLog metadata.xml cacti-0.8.7a-r2.ebuild cacti-0.8.6j-r8.ebuild cacti-0.8.7b.ebuild cacti-0.8.7a-r1.ebuild cacti-0.8.7a.ebuild
Date: Thu, 14 Feb 2008 23:19:31 -0800	[thread overview]
Message-ID: <20080215071930.GC26221@supernova> (raw)
In-Reply-To: <E1JPHDc-0001hG-Pu@stork.gentoo.org>

On 13:00 Wed 13 Feb     , Peter Volkov (pva) wrote:
> 1.1                  net-analyzer/cacti/cacti-0.8.7a-r2.ebuild
> 
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-analyzer/cacti/cacti-0.8.7a-r2.ebuild?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-analyzer/cacti/cacti-0.8.7a-r2.ebuild?rev=1.1&content-type=text/plain

> IUSE="snmp bundled-adodb"

> 	!bundled-adodb? ( dev-php/adodb )

> 	use bundled-adodb || sed -i -e \
> 	's:$config\["library_path"\] . "/adodb/adodb.inc.php":"adodb/adodb.inc.php":' \
> 	"${S}"/include/global.php

> 	use bundled-adodb || phpUseFlags="${phpUseFlags} sockets"

Why is bundling even an option? We should always force external packages 
to be used, or we end up with more zlib messes.

Thanks,
Donnie
-- 
gentoo-dev@lists.gentoo.org mailing list



       reply	other threads:[~2008-02-15  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1JPHDc-0001hG-Pu@stork.gentoo.org>
2008-02-15  7:19 ` Donnie Berkholz [this message]
2008-02-16 12:25   ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/cacti: ChangeLog metadata.xml cacti-0.8.7a-r2.ebuild cacti-0.8.6j-r8.ebuild cacti-0.8.7b.ebuild cacti-0.8.7a-r1.ebuild cacti-0.8.7a.ebuild Peter Volkov
2008-02-16 12:30     ` Ciaran McCreesh
2008-02-16 21:46     ` Donnie Berkholz

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=20080215071930.GC26221@supernova \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pva@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