Re: [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

2008-02-16 Thread Ciaran McCreesh
On Sat, 16 Feb 2008 15:25:43 +0300
Peter Volkov [EMAIL PROTECTED] wrote:
 This does no harm and can help in situations when web-app upstream
 modified bundled adodb in non compatible way. But well, I'll drop it
 from USE flags and define environmental variable inside ebuild to show
 that although there is possibility to use bundled adodb it's not
 supported.

A USE flag is better than an environment variable. Environment
variables aren't easily visible to the end user beforehand.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [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

2008-02-16 Thread Donnie Berkholz
On 15:25 Sat 16 Feb , Peter Volkov wrote:
 В Чтв, 14/02/2008 в 23:19 -0800, Donnie Berkholz пишет: 
 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.
 
 This does no harm and can help in situations when web-app upstream
 modified bundled adodb in non compatible way.

It does do harm. It prevents our package management system from doing 
what it's there to do.

If they're modifying the bundled adodb incompatibly, then the USE flag 
would also be obsolete because you'd need to force it to be bundled. 
What would help more is a good swift kick in the pants to the people 
doing the modifying to tell them to send their changes to adodb 
upstream.

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