From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1IBxAP-0000ZG-NQ for garchives@archives.gentoo.org; Fri, 20 Jul 2007 18:25:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6KINQYi002338; Fri, 20 Jul 2007 18:23:26 GMT Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l6KIK7Gg029884 for ; Fri, 20 Jul 2007 18:20:07 GMT Received: by wa-out-1112.google.com with SMTP id k34so1052403wah for ; Fri, 20 Jul 2007 11:20:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=czw7v94hIBrf7eIc+Q8MKzZHQEMIoTWxn7okhSpRR09RW6SX1Ne+ZHQF+Ah0QAmNKFzBmdGJ4qazZ8SlPAcsA2tBpJKC5zGPPveRP6B1j97wZYh4I2k2DZYE2uGJr/5NlbJlfyYEe4yY6khExe9RLOEZjP0f5CD2sAl0DLqA0R0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tDTjxevKCuIOriFkTsSXEZzYKgvy+Wpzu1NzhFwt9BMb572kQB9Ez+41k4LedWCIvUHtv+VIycCctf6NG96ZXtBLGI3N3MmJFOBJcDmNyD8fnzZ3bttUZib3FHWyR9dKbfJLvP0t+lTKsES2pZkTgxLCA8L+pRmKDjiDQVmnwE8= Received: by 10.114.149.2 with SMTP id w2mr733635wad.1184955606567; Fri, 20 Jul 2007 11:20:06 -0700 (PDT) Received: by 10.115.18.13 with HTTP; Fri, 20 Jul 2007 11:20:06 -0700 (PDT) Message-ID: Date: Fri, 20 Jul 2007 14:20:06 -0400 From: "Eric Polino" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: net-im/pidgin protocols In-Reply-To: <20070720110328.38b52336@sed-192.sedsystems.ca> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <469F1C56.6070600@gentoo.org> <469F372A.9060107@gentoo.org> <469F3A9F.7030004@gentoo.org> <46A0DE7B.6030009@gentoo.org> <46A0C2A9.4090100@fire-eyes.org> <20070720110328.38b52336@sed-192.sedsystems.ca> X-Archives-Salt: c4be805f-0b76-4901-a59c-206df43529b0 X-Archives-Hash: decde362e6160b5a74bfc6ed5149371e It would seem there is a good support for a change to enable all protocols by default. What will change this issue from a good thread to an action on the package to implement these ideas? Another suggestion brought to me by an upstream dev was that Pidgin is configured to install all protocols by default. If the required libraries for a protocol is missing, ie: gadu, zephyr, silc, bonjour, then Pidgin builds/runs fine and that protocol isn't available for the user to use. Not wanting to alienate those who use these protocols, but they aren't very common to begin with, so this will only apply to a small sample of users. So a warning could be put in the ewarn saying that if you want there protos you have to install their required libs. I don't think this is a bad idea. I've seen a few packages do that before. This way we don't pull in unwanted dependencies. This could be coupled with the idea of negative USE flags, though nasty and unwanted, I think like someone mentioned a bit earlier, they stand out and are more effective when it comes to this type of situation involving defaults. Summary: 1. Switch all USE flags to negative USE flags. 2. Don't install deps for protocols (maybe still install SSL) 3. Put a message in the ewarn about missing libs for extra protos. Once again, how does this thread move to action on the package? Can I call "Question"? ;) Thanks, Eric On 7/20/07, Jim Ramsay wrote: > fire-eyes wrote: > > Duncan wrote: > > > OTOH, if enabling those protocols pulls in all sorts of additional > > > packages to support them, shipping with everything on just because > > > it's possible is not the Gentoo way. That's what USE flags are > > > for. If indeed additional dependencies are pulled in, IMO the USE > > > flags should remain, and maybe someone needs to explain the Gentoo > > > way to upstream. > > > > ++; from a user. I prefer to leave them off. However I can understand > > the other sides point of view, too. > > I believe one of the main philosophies of Gentoo is to try to have an > app be as close to upstream as possible. I personally believe that > this means the we should try to enable enough USE flags by default that > it is roughly equivalent to running upstream's './configure' with no > arguments. USE flags then give the advanced user the ability to > disable those features normally on, or enable those features normally > off, but we want a freshly installed package by default to "just > work"[1] and to be "as close to upstream as possible"[2]. > > With this in mind, enabling most of the default protocols makes sense > to me. > > [1] > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap1 > > [2] looking for actual references to this, but couldn't find it... > I think it's _somewhere_ in the required new-developer reading... > > -- > Jim Ramsay > Gentoo/Linux Developer (rox,gkrellm) > > -- http://aluink.blogspot.com -- "...indexable arrays, which may be thought of as functions whose domains are isomorphic to contiguous subsets of the integers." --Haskell 98 Library Report -- gentoo-dev@gentoo.org mailing list