Re: [gentoo-dev] Gentoo
On 7/18/07, Michael Sullivan [EMAIL PROTECTED] wrote:
On Fri, 2007-07-13 at 07:16 -0500, Rick Sivernell wrote:
I am trying to contact somebody in charge of gentoo. I have tried for years
now to get my email address off your list, but all has failed. If someone knows
this person or will send me the email address so that I may contact them, I would
appreciate this. Currently this is eating our bandwidth and I am sending all to
the trash bin now.
--
Rick Sivernell
Dallas, Texas 75287
972 306-2296
[EMAIL PROTECTED]
Registered Linux User
Wow. You've been trying to get off this list for YEARS? And the
unsubscribe information has been in the headers of every email this list
sends out. You must feel pretty foolish about now. BTW, it's not the
list administrator's job to unsubscribe people.
-Michael Sullivan-
--
[EMAIL PROTECTED] mailing list
For the sake of ricks ease of seeing:
List-Post: mailto:gentoo-dev@lists.gentoo.org
List-Help: mailto:[EMAIL PROTECTED]
List-Unsubscribe: mailto:[EMAIL PROTECTED]
List-Subscribe: mailto:[EMAIL PROTECTED]
List-Id: Gentoo Linux mail gentoo-dev.gentoo.org
( just in case his email client was dull and didn't show him )
( I myself never knew they were there untill you pointed this fact out. )
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print enNOSPicAMreil [EMAIL PROTECTED][(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: [gentoo-council] Nominations open for the Gentoo Council 2007/08
Mike Frysinger wrote: i dont think he'll accept, but i dont see Flameeyes name yet ... -mike +1 -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Paludis and Emacs overlay
On Tue, 17 Jul 2007 21:31:50 +0200 Christian Faulhammer [EMAIL PROTECTED] wrote: I just read Donnie's nice article [1] and went through the comments. One saying After switching to paludis, I installed layman, and used it to kick-start some of the overlays.gentoo.org stuff. Paludis expects more discipline, apparently, and there was some manual effort to configure, say, the emacs overlay. Had to create several files and directories to silence the error traces. Can anyone tell me what those messages actually are to fix it? Hrm, I don't see any warnings for the emacs overlay using the following (native, not Portage) configuration: location = /var/paludis/repositories/emacs format = ebuild sync = svn+http://overlays.gentoo.org/svn/proj/emacs/emacs-overlay master_repository = gentoo write_cache = /var/cache/paludis/metadata/ Usually when people get errors with an overlay it's because of a missing profiles/repo_name file, which isn't the case here. -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] x86 toolchain changes heads up
On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. -mike Does this mean that any user-set -march flag is overridden for these cases? Just curious. Thanks. -- Peter Gordon (codergeek42) Gentoo Forums Global Moderator GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] x86 toolchain changes heads up
I think it's the other way arround. -march=ix86 is implicit unless you override it with a user variable. On 7/18/07, Peter Gordon [EMAIL PROTECTED] wrote: On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. -mike Does this mean that any user-set -march flag is overridden for these cases? Just curious. Thanks. -- Peter Gordon (codergeek42) Gentoo Forums Global Moderator GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ -- Ioannis Aslanidis deathwing00[at]gentoo.org 0xB9B11F4E -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] x86 toolchain changes heads up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Gordon wrote: On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. -mike Does this mean that any user-set -march flag is overridden for these cases? Just curious. I think he meant CHOST sets just *default* so any user-set -march overrides that. But I wonder what happens to user-set -mtune then? Since AFAIK -march implies -mtune, will also the default -march override user-set -mtune? - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGndsrtbrAj05h3oQRAp5hAJ4in2JnV637D7GyDMvG6hc8A8/n4QCeK9Eo IFUTZxAFqfSVx3Za64GQM0c= =6wSA -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Paludis and Emacs overlay
On Wed, 18 Jul 2007, Ciaran McCreesh wrote: Hrm, I don't see any warnings for the emacs overlay [...] Usually when people get errors with an overlay it's because of a missing profiles/repo_name file, which isn't the case here. It might well be the reason since the comment on LWN is from 5 July and the file didn't exist at the time: $ svn log emacs-overlay/profiles/repo_name r579 | ulm | 2007-07-09 21:16:41 +0200 (Mon, 09 Jul 2007) | 2 lines Add profiles/repo_name. Ulrich -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] x86 toolchain changes heads up
Peter Gordon wrote: On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. -mike Does this mean that any user-set -march flag is overridden for these cases? Just curious. You quoted the answer :) These flags are merely the default. Any user-specified flags will override the default. For example, if you have CFLAGS=-march=i586 with a i686 CHOST, it'd be effectively like calling gcc with 'gcc -march=i686 -march=i586'. The later option would win. -- Andrew Gaffney http://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Catalyst/Installer + x86 release coordinator -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] x86 toolchain changes heads up
On Wednesday 18 July 2007, Peter Gordon wrote: On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. -mike Does this mean that any user-set -march flag is overridden for these cases? Just curious. *cough* keep in mind this is merely the default *cough* -mike signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Re: x86 toolchain changes heads up
Vlastimil Babka wrote:
Peter Gordon wrote:
On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote:
historically, gcc on x86 has always defaulted to i386. some people noticed
recently that glibc-2.6 fails to build in this situation as they were only
setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it
will
default -march based on your CHOST. so all the i686-* people will now have
a
default -march=i686 implied in their gcc systems, i586-* people will
have -march=i586, etc... keep in mind this is merely the default.
-mike
Does this mean that any user-set -march flag is overridden for these
cases? Just curious.
I think he meant CHOST sets just *default* so any user-set -march
overrides that.
But I wonder what happens to user-set -mtune then? Since AFAIK -march
implies -mtune, will also the default -march override user-set -mtune?
Previously GCC defaulted to -march=i386, which implied -mtune=i386
(actually, -mcpu for some reason (?)), when neither were set. People
are setting CFLAGS=-mtune=pentium4 -O2 -fblah... which therefore is
defaulting to -march=i386 -mtune=pentium4. glibc-2.6 requires =
-march=i486. Kaboom.
Now -march=$(echo $CHOST | awk -F- '{ print $1 }'), which implies
-mtune=echo $CHOST | awk -F- '{ print $1 }' when neither are set. If
_either_ are set by the user, they are overridden.
ie. you can still set -march=i386 or -mtune=i386 or whatever you like.
--
dirtyepic salesman said this vacuum's guaranteed
gentoo org it could suck an ancient virus from the sea
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8)
--
[EMAIL PROTECTED] mailing list
[gentoo-dev] Re: Getting -project started
Kumba [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 17 Jul 2007 09:50:26 -0400: George Prowse wrote: So that would mean that welcoming new developers would be on the -project list? My thinking, I think they would fit better over there, since it is somewhat non-technical. However, machine-generated notices of dev arrival or dev departure could be directed to other lists. There's been talk of a -dev-announce list as well; perhaps such automated messages of dev changes could be sent there in a fashion (either individually as one joins or one leaves, or in a weekly digest form summarizing the changes). According to the bug on -project (which I was CCed to), both it and dev- announce have been created. New developers are announcements. The primary announcement should therefore go to dev-announce, x-posted to dev, with followups going to -project, since the followups are neither announcements nor dev-technical and thus don't belong on either dev-announce or dev. Would package removals be on it because it seems to be somewhere in the middle? I think package additions/removals should stay there, since they are development related, such as the removal due to bitrot or an unfixiable security flaw, etc. Such messages might also be candidates for the above mentioned -dev-announce ML as well. Similarly here, the additions-removals initial post should go on dev- announce (x-posted to dev, of course, as anything there should be, so those that choose to can read only dev), with replies sent to dev. Additions-removals doesn't get many replies, but last-rites mails are in the same category and do. Replies to last-rites are dev material. Do note, however, that when a last-rites is actually canceled, that's an announcement that then belongs on dev-announce (xposted and followups to dev). That's my take on it, anyway. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Re: Getting -project started
Philip Webb [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 17 Jul 2007 23:28:57 -0400: To this user since 2003, who plans to install Gentoo in the new machine which I am presently designing, this sounds like a very welcome development. I shall continue to subscribe to -dev , but not to -project. Should I also subscribe to -dev-announce or will its msgs be duplicated on -dev ? You may in fact wish to subscribe to gentoo-project after all, as there are a lot of people (myself included) hoping the traffic on -dev goes down by at least 50%. I'm seriously hoping there'll be few non-dev posts to dev, as while IMO non-devs should be free to post to -dev, it should be development-technical only. I hope peer pressure forces that, with a simple reminder that -project gets everything else, for any violators. IOW, both your post and mine should now be going to -project (I expect to be subscribing shortly). Ideally, there'll be little reason for us to post to dev, tho I hope it remains such that we can. If it works, there'll be little reason to go further with that moderation proposal. So, unless you plan on being read-only on Gentoo discussions, I'd suggest you do subscribe to -project, and strongly consider posting much of what you've posted here in the past, there. That's what I'll be doing. If it fails to work that way by peer pressure, it's likely to end up almost forced that way, and I really hate to see that happen. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: Getting -project started
Duncan wrote: Philip Webb [EMAIL PROTECTED] posted: To this user since 2003, who plans to install Gentoo in the new machine which I am presently designing, this sounds like a very welcome development. I shall continue to subscribe to -dev , but not to -project. Should I also subscribe to -dev-announce or will its msgs be duplicated on -dev ? You may in fact wish to subscribe to gentoo-project after all, as there are a lot of people (myself included) hoping the traffic on -dev goes down by at least 50%. I'm seriously hoping there'll be few non-dev posts to dev, as while IMO non-devs should be free to post to -dev, it should be development-technical only. I hope peer pressure forces that, with a simple reminder that -project gets everything else, for any violators. IOW, both your post and mine should now be going to -project (I expect to be subscribing shortly). Ideally, there'll be little reason for us to post to dev, tho I hope it remains such that we can. If it works, there'll be little reason to go further with that moderation proposal. So, unless you plan on being read-only on Gentoo discussions, I'd suggest you do subscribe to -project, and strongly consider posting much of what you've posted here in the past, there. That's what I'll be doing. If it fails to work that way by peer pressure, it's likely to end up almost forced that way, and I really hate to see that happen. It looks like what Philip is also asking here is whether he should subscribe to *both* -dev *and* -dev-announce. I am curious about this as well. It depends on whether all messages to -dev-announce are relayed to -dev automatically. If so, then the user would want to subscribe to *one* of the lists, not both. If not, then users would want to subscribe to both lists if they want all traffic. I suspect not is the way it was set up, since clearly all posts to the new -dev-announce will not be technical, and so they should not be relayed to -dev automatically. Anyone know? -Joe P.S. Duncan, +1 on your comments about use of the lists! -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: Getting -project started
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Duncan wrote: According to the bug on -project (which I was CCed to), both it and dev- announce have been created. New developers are announcements. The primary announcement should therefore go to dev-announce, x-posted to dev, with followups going to -project, since the followups are neither announcements nor dev-technical and thus don't belong on either dev-announce or dev. Similarly here, the additions-removals initial post should go on dev- announce (x-posted to dev, of course, as anything there should be, so those that choose to can read only dev), with replies sent to dev. Additions-removals doesn't get many replies, but last-rites mails are in the same category and do. Replies to last-rites are dev material. ... That's my take on it, anyway. [crossposting to -project to facilitate moving this thread over] As usual, good ideas. One thing I'd say is that just because everything isn't 100% figured it there is no reason not to start using the new lists. And we can all try to be patient if somebody posts to the wrong lists while things are being worked out. I'm sure practices will evolve as makes sense. Let's hope this initiative works out well! If the need for moderation is mooted I think everybody will be happy! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGnlL9G4/rWKZmVWkRAoCzAKCw+FWM05K3bE5vm25zrmtijH2cNwCgztVh x2b59MY1CxMuOHdKWN6zBUQ= =T45h -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-dev] Re: Getting -project started
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joe Peterson wrote: I suspect not is the way it was set up, since clearly all posts to the new -dev-announce will not be technical, and so they should not be relayed to -dev automatically. Anyone know? I like the idea of auto-crossposting, but for those who need it here is a nice procmail recipe to handle either case: :0 Wh: msgid.lock | formail -D 8192 msgid.cache :0 a: /dev/null This maintains an 8k cache of message IDs and tosses any message it has already seen. Then you can send both -dev and -dev-announce to the same folder and get every message once. If you're like me and have 14 email addresses forwarded to the same box the rule is invaluable in general. Note - I'm not responsible if the code above destroys your system or loses mail - understand procmail before you use it... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGnln+G4/rWKZmVWkRAtP9AKCbBVq97mw5LA0CjhaExvn7O8YqGACfY1RQ /3awXBPpZfy0LfNVIaOMXuw= =8oKZ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
[gentoo-dev] Lastrite: media-libs/janus
# Samuli Suominen [EMAIL PROTECTED] (18 Jul 2007) # Masked for treecleaners bug 185386. Unfetchable package, # homepage is unavailable and for using GTK+-1.2. # Removed in 60 days. media-libs/janus It actually redirects you to Disney travel agency pages from homepage. *g* -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] x86 toolchain changes heads up
On Tue, 2007-07-17 at 19:47 -0400, Mike Frysinger wrote: historically, gcc on x86 has always defaulted to i386. some people noticed recently that glibc-2.6 fails to build in this situation as they were only setting -mtune via CFLAGS, not -march. i'll be tweaking gcc so that it will default -march based on your CHOST. so all the i686-* people will now have a default -march=i686 implied in their gcc systems, i586-* people will have -march=i586, etc... keep in mind this is merely the default. Have you spoken with upstream about this? Is there any way they would adopt it there? -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
[gentoo-dev] Council Nominations
All,
You've all stated that you accept or don't accept (but this is targeted
at the acceptors, sorry non-acceptors) but the people that accept
haven't really given much reason as to why they would be a good
candidate. In fact many of the nominations don't even have that
information attached. Because right now, no one has earned my vote. If
it came down to voting right now, I'd have to side with all the American
Republicans in the crowd and vote None of the Above [1] [2].
So, let's hear some reasons why I as a Gentoo developer should vote for
you. And here's a hint, be more forward looking then the current 100+
post threads on the -dev ML. Let's hear your {2,3,5} year plan for Gentoo.
For the sake of everyone's sanity, please don't reply directly to this
thread. Please start a new thread that states So and So's Platform or
some such. Also, if you want to blog it or put it on your dev webspace
it might be a better idea. That being said, that means there should be
no replies to this thread.
[1] http://www.fark.com
[2]
http://news.yahoo.com/s/ap/20070717/ap_on_el_pr/presidential_race_ap_poll
--
Doug Goldstein
--
[EMAIL PROTECTED] mailing list
[gentoo-dev] Re: Council Nominations
* Doug Goldstein [EMAIL PROTECTED]:
So, let's hear some reasons why I as a Gentoo developer should vote for
you. And here's a hint, be more forward looking then the current 100+
post threads on the -dev ML. Let's hear your {2,3,5} year plan for Gentoo.
Sounds good.
For the sake of everyone's sanity, please don't reply directly to this
thread. Please start a new thread that states So and So's Platform or
some such. Also, if you want to blog it or put it on your dev webspace
it might be a better idea. That being said, that means there should be
no replies to this thread.
I do ignore it and reply anyway:
- because the statments can/should be archived in council's project
space (see the nomination list of 2005). Details need to be worked
out.
I think blog links don't work very well here.
- and since today we have the project list. I think these statements
should be send to -project (or is it an announcement and should go to
-dev-announce with follow ups to -project?)
Thanks.
--
[EMAIL PROTECTED] mailing list
[gentoo-dev] Zombie: Sven Vermeulen (swift)
Your doc zombie Sven Vermeulen has risen from his grave and is back to beat www.gentoo.org/doc/en with his fingers. Give him the usual welcome with nice head shots. Regards, Petteri PS. I tried but couldn't get myself subscribed to -dev-announce yet but maybe before the next one :) signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: Getting -project started
On Wed, Jul 18, 2007 at 02:20:46PM -0400, Richard Freeman wrote: :0 Wh: msgid.lock | formail -D 8192 msgid.cache :0 a: /dev/null I'd advise against this bit of procmail hackery. I used to use it, until I ran into some MUAs that did not generate sane message-ids (Lotus Notes, certain versions of Outlook, and some Linux clients at various points in time). Collisions in message-ids are bad! -- Robin Hugh Johnson Gentoo Linux Developer Council Member E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpQ3wQfSUpT4.pgp Description: PGP signature
Re: [gentoo-dev] Zombie: Sven Vermeulen (swift)
Il Wednesday 18 July 2007 23:22:56 Petteri Räty ha scritto: Your doc zombie Sven Vermeulen has risen from his grave and is back to beat www.gentoo.org/doc/en with his fingers. Give him the usual welcome with nice head shots. Regards, Petteri PS. I tried but couldn't get myself subscribed to -dev-announce yet but maybe before the next one :) Wow, it's a WONDERFUL news 8) Welcome back swift, it's an honour for me working aside you ;) /me bow to the elder doc dev -- Davide Cendron Gentoo Documentation Project Italian Lead Translator http://www.gentoo.org/doc/it/ signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Zombie: Sven Vermeulen (swift)
Petteri Räty wrote: Your doc zombie Sven Vermeulen has risen from his grave and is back to beat www.gentoo.org/doc/en with his fingers. Give him the usual welcome with nice head shots. Welcome back, Sven :) Kind Regards, -- Dimitry Bradt - [EMAIL PROTECTED] Gentoo/Linux Developer -- signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Zombie: Sven Vermeulen (swift)
On 7/18/07, Petteri Räty [EMAIL PROTECTED] wrote: Your doc zombie Sven Vermeulen has risen from his grave and is back to beat www.gentoo.org/doc/en with his fingers. Give him the usual welcome with nice head shots. Welcome back Sven! Btw, you should be nominated for Council because of bug #27727, comment #2 ;-) -- Santiago M. Mola Jabber ID: [EMAIL PROTECTED]
Re: [gentoo-dev] Zombie: Sven Vermeulen (swift)
Petteri Räty wrote: Your doc zombie Sven Vermeulen has risen from his grave and is back to beat www.gentoo.org/doc/en with his fingers. Give him the usual welcome with nice head shots. Hi SwifTy. See you 'round our channel! signature.asc Description: OpenPGP digital signature
[gentoo-dev] net-im/pidgin protocols
Would it be possible to have all the protocols for net-im/pidgin turned on by default. We often get people coming to #pidgin looking for help as to why they can't get MSN or some other protocol working. It most often is because they haven't enabled the given protocol USE flag. There is nothing gained in turning a protocol off. At the very most you might save on 100K of memory, and a small amount of compile time (pidgin takes a good while to compile, so this is a small percentage). On the other hand, by having them off by default, people often lose a lot of time figuring out why they are missing some protocol. Finding out which ones they want, setting up package.use... The wanted gain is lost in research and setup time. I would understand if they were huge aspects of the application that took up tons of HD space, tons of RAM and took a while to compile, but they aren't. I have two suggestions for solutions. The protocol flags could be removed and would make them on all the time. Or if the overzealous user insists on having some off, there could be negative flags such as nomsn, noaim, etc. I am busy with a GSoC project right now, but I can offer a diff for an ebuild that would provide this functionality once I find time to. Thanks, Eric -- 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 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] net-im/pidgin protocols
On 7/19/07, Caleb Cushing [EMAIL PROTECTED] wrote: another option could just be to enable the protocols in the ebuild by default (or does that have to be done globally in profile?) and force users to turn them off if they don't want them. Yeah that would have to be done in the profile. We could have extended use flags added that are on by default in the profile. Though I would think this to be overkill for this problem. On 7/19/07, Eric Polino [EMAIL PROTECTED] wrote: Would it be possible to have all the protocols for net-im/pidgin turned on by default. We often get people coming to #pidgin looking for help as to why they can't get MSN or some other protocol working. It most often is because they haven't enabled the given protocol USE flag. There is nothing gained in turning a protocol off. At the very most you might save on 100K of memory, and a small amount of compile time (pidgin takes a good while to compile, so this is a small percentage). On the other hand, by having them off by default, people often lose a lot of time figuring out why they are missing some protocol. Finding out which ones they want, setting up package.use... The wanted gain is lost in research and setup time. I would understand if they were huge aspects of the application that took up tons of HD space, tons of RAM and took a while to compile, but they aren't. I have two suggestions for solutions. The protocol flags could be removed and would make them on all the time. Or if the overzealous user insists on having some off, there could be negative flags such as nomsn, noaim, etc. I am busy with a GSoC project right now, but I can offer a diff for an ebuild that would provide this functionality once I find time to. Thanks, Eric -- 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 -- [EMAIL PROTECTED] mailing list -- Caleb Cushing -- 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 -- [EMAIL PROTECTED] mailing list
