[gentoo-dev] moving USE=server to global
On Saturday 17 March 2007, Steve Long wrote: Piotr Jaroszy?ski wrote: I have heard about the magic limit of 5, but whatever... Is there a *technical* objection then to server? if you're going to change the topic mid-thread, then you should update the subject you already know the state of the server/client debate ... moving it to global doesnt fix any of the short comings, so it should stay local (and removed where possible) -mike pgps9A82YkEo1.pgp Description: PGP signature
Re: [gentoo-dev] [RFC] removal of /etc/dev.d - cleanup of /etc/udev/rules.d/
On Donnerstag, 15. März 2007, Matthias Schwarzott wrote: Hi fellows! 2. I think we should get udev rules directory (/etc/udev/rules.d/) a bit more cleaned up. At the moment a lot of packages install their files prefixed with 99. I does not like that, and in the future that should perhaps be moved to some numbers below 95, as I hope to get 95-udev-late.rules to be the last one called. This is a (possibly incomplete) list of ebuilds installing udev-rules: app-crypt/ccid-1.2.0.ebuild: 60-pcscd_ccid.rules app-crypt/ccid-1.2.1.ebuild: 60-pcscd_ccid.rules app-misc/lirc-0.8.1: 10-lirc.rules app-misc/lirc-0.8.0-r5: 10-lirc.rules app-misc/lirc-0.8.0-r8: 10-lirc.rules app-misc/usbirboy-0.2.1-r1: 55-usbirboy.rules sys-power/nut-2.0.5: 70-nut-usbups.rules sys-power/nut-2.0.5-r1: 70-nut-usbups.rules sys-power/nut-2.0.4: 70-nut-usbups.rules sys-power/nut-2.0.4-r1: 70-nut-usbups.rules sys-power/nut-2.0.3: 70-nut-usbups.rules sys-power/nut-2.0.3-r1: 70-nut-usbups.rules media-gfx/iscan-2.2.0-r1: 75-iscan.rules media-gfx/iscan-2.4.0: 75-iscan.rules media-gfx/iscan-2.4.0-r1: 99-iscan.rules media-gfx/sane-backends-1.0.18-r2: 99-libsane.rules media-libs/libgphoto2-2.3.1-r3: 99-libgphoto2.rules media-libs/libgphoto2-2.3.1-r2: 99-libgphoto2.rules media-libs/libgphoto2-2.2.1-r1: 99-libgphoto2.rules media-libs/libgphoto2-2.3.1-r4: 99-libgphoto2.rules media-libs/svgalib-1.9.25: 30-svgalib.rules media-libs/svgalib-1.9.24: 30-svgalib.rules media-libs/libmtp-0.1.3: 65-mtp.rules media-libs/libmtp-0.0.21: 65-mtp.rules sys-apps/pcfclock-0.44-r3: 55-pcfclock.rules sys-apps/pcfclock-0.44-r2: 55-pcfclock.rules sys-auth/bioapi-1.2.2: 51-bioapi.rules app-emulation/virtualbox-modules-1.3.6-r1: 60-virtualbox.rules app-emulation/virtualbox-modules-1.3.8: 60-virtualbox.rules app-emulation/virtualbox-: 60-virtualbox.rules app-emulation/kqemu-1.3.0_pre9: 48-qemu.rules app-emulation/kqemu-0.7.2: 48-qemu.rules app-emulation/kqemu-1.3.0_pre5: 48-qemu.rules app-emulation/kqemu-1.3.0_pre11: 48-qemu.rules app-emulation/kqemu-1.3.0_pre7: 48-qemu.rules net-misc/zaptel-1.2.11-r1: 10-zaptel.rules net-misc/zaptel-1.0.10-r2: 10-zaptel.rules net-misc/zaptel-1.2.9.1-r1: 10-zaptel.rules net-misc/zaptel-1.2.12-r1: 10-zaptel.rules net-misc/zaptel-1.2.12: 10-zaptel.rules dev-libs/legousbtower-0.5.4: 20-lego.rules dev-libs/openct-0.6.11-r1: 70-openct.rules dev-libs/linux-fusion-3.2-r1: 60-fusion.rules net-wireless/bluez-utils-2.24: 70-bluetooth.rules net-wireless/bluez-utils-2.25-r1: 70-bluetooth.rules sys-fs/cowloop-2.15-r1: 70-cow.rules sys-fs/cowloop-3.0-r2: 70-cow.rules sys-fs/multipath-tools-0.4.7-r1: 40-multipath.rules media-sound/alsa-firmware-1.0.14_rc3: 52-usx2yaudio.rules media-sound/alsa-firmware-1.0.14_rc2-r1: 52-usx2yaudio.rules media-video/em8300-modules-0.15.3: 15-em8300.rules media-video/em8300-modules-0.16.0-r1: 15-em8300.rules app-antivirus/clamav-0.88.7-r2: 60-dazuko.rules app-antivirus/clamav-0.88.7-r1: 60-dazuko.rules net-dialup/misdn-1.0.4: 53-misdn.rules net-dialup/slmodem-2.9.11_pre20061021-r2: 55-slmodem.rules net-dialup/ltmodem-8.31_alpha10-r3: 55-ltmodem.rules media-tv/wis-go7007-0.9.8: wis-ezusb.rules If you maintain such a package can you please check if the rules use no syntax-elements being deprecated, and going to be removed in future udev-versions, like BUS: replaced by SUBSYSTEM/SUBSYSTEMS SYSFS: replaced by ATTR/ATTRS or others. These packages even checks for /dev/.udev existence to install rules files: I think that they should unconditionally install that file. sys-apps/pcfclock-0.44-r3 sys-apps/pcfclock-0.44-r2 Matthias -- Matthias Schwarzott (zzam) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] [RFC] removal of /etc/dev.d - cleanup of /etc/udev/rules.d/
maillog: 18/03/2007-10:57:01(+0100): Matthias Schwarzott types On Donnerstag, 15. März 2007, Matthias Schwarzott wrote: Hi fellows! 2. I think we should get udev rules directory (/etc/udev/rules.d/) a bit more cleaned up. At the moment a lot of packages install their files prefixed with 99. I does not like that, and in the future that should perhaps be moved to some numbers below 95, as I hope to get 95-udev-late.rules to be the last one called. This is a (possibly incomplete) list of ebuilds installing udev-rules: app-crypt/ccid-1.2.0.ebuild: 60-pcscd_ccid.rules app-crypt/ccid-1.2.1.ebuild: 60-pcscd_ccid.rules app-misc/lirc-0.8.1: 10-lirc.rules app-misc/lirc-0.8.0-r5: 10-lirc.rules app-misc/lirc-0.8.0-r8: 10-lirc.rules app-misc/usbirboy-0.2.1-r1: 55-usbirboy.rules sys-power/nut-2.0.5: 70-nut-usbups.rules sys-power/nut-2.0.5-r1: 70-nut-usbups.rules sys-power/nut-2.0.4: 70-nut-usbups.rules sys-power/nut-2.0.4-r1: 70-nut-usbups.rules sys-power/nut-2.0.3: 70-nut-usbups.rules sys-power/nut-2.0.3-r1: 70-nut-usbups.rules media-gfx/iscan-2.2.0-r1: 75-iscan.rules media-gfx/iscan-2.4.0: 75-iscan.rules media-gfx/iscan-2.4.0-r1: 99-iscan.rules media-gfx/sane-backends-1.0.18-r2: 99-libsane.rules media-libs/libgphoto2-2.3.1-r3: 99-libgphoto2.rules media-libs/libgphoto2-2.3.1-r2: 99-libgphoto2.rules media-libs/libgphoto2-2.2.1-r1: 99-libgphoto2.rules media-libs/libgphoto2-2.3.1-r4: 99-libgphoto2.rules media-libs/svgalib-1.9.25: 30-svgalib.rules media-libs/svgalib-1.9.24: 30-svgalib.rules media-libs/libmtp-0.1.3: 65-mtp.rules media-libs/libmtp-0.0.21: 65-mtp.rules sys-apps/pcfclock-0.44-r3: 55-pcfclock.rules sys-apps/pcfclock-0.44-r2: 55-pcfclock.rules sys-auth/bioapi-1.2.2: 51-bioapi.rules app-emulation/virtualbox-modules-1.3.6-r1: 60-virtualbox.rules app-emulation/virtualbox-modules-1.3.8: 60-virtualbox.rules app-emulation/virtualbox-: 60-virtualbox.rules app-emulation/kqemu-1.3.0_pre9: 48-qemu.rules app-emulation/kqemu-0.7.2: 48-qemu.rules app-emulation/kqemu-1.3.0_pre5: 48-qemu.rules app-emulation/kqemu-1.3.0_pre11: 48-qemu.rules app-emulation/kqemu-1.3.0_pre7: 48-qemu.rules net-misc/zaptel-1.2.11-r1: 10-zaptel.rules net-misc/zaptel-1.0.10-r2: 10-zaptel.rules net-misc/zaptel-1.2.9.1-r1: 10-zaptel.rules net-misc/zaptel-1.2.12-r1: 10-zaptel.rules net-misc/zaptel-1.2.12: 10-zaptel.rules dev-libs/legousbtower-0.5.4: 20-lego.rules dev-libs/openct-0.6.11-r1: 70-openct.rules dev-libs/linux-fusion-3.2-r1: 60-fusion.rules net-wireless/bluez-utils-2.24: 70-bluetooth.rules net-wireless/bluez-utils-2.25-r1: 70-bluetooth.rules sys-fs/cowloop-2.15-r1: 70-cow.rules sys-fs/cowloop-3.0-r2: 70-cow.rules sys-fs/multipath-tools-0.4.7-r1: 40-multipath.rules media-sound/alsa-firmware-1.0.14_rc3: 52-usx2yaudio.rules media-sound/alsa-firmware-1.0.14_rc2-r1: 52-usx2yaudio.rules media-video/em8300-modules-0.15.3: 15-em8300.rules media-video/em8300-modules-0.16.0-r1: 15-em8300.rules app-antivirus/clamav-0.88.7-r2: 60-dazuko.rules app-antivirus/clamav-0.88.7-r1: 60-dazuko.rules net-dialup/misdn-1.0.4: 53-misdn.rules net-dialup/slmodem-2.9.11_pre20061021-r2: 55-slmodem.rules net-dialup/ltmodem-8.31_alpha10-r3: 55-ltmodem.rules media-tv/wis-go7007-0.9.8: wis-ezusb.rules app-emulation/vmware-modules-*: 60-vmware.rules If you maintain such a package can you please check if the rules use no syntax-elements being deprecated, and going to be removed in future udev-versions, like BUS: replaced by SUBSYSTEM/SUBSYSTEMS SYSFS: replaced by ATTR/ATTRS or others. These packages even checks for /dev/.udev existence to install rules files: I think that they should unconditionally install that file. sys-apps/pcfclock-0.44-r3 sys-apps/pcfclock-0.44-r2 -- / Georgi Georgiev/ What fools these mortals be. -- Lucius / \ [EMAIL PROTECTED]\ Annaeus Seneca \ / http://www.gg3.net/ / / -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] About testing applications
Many applications save preferences in ~/.app/. When testing applications please make sure you test with an empty directory to catch cases when an upgrade works fine but a clean install doesn't. Thanks. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] About testing applications
Petteri Räty wrote: Many applications save preferences in ~/.app/. When testing applications please make sure you test with an empty directory to catch cases when an upgrade works fine but a clean install doesn't. Thanks. Even better: Fix them to use ~/.config/app instead, so they don't clutter up the home unnecessarily :) -- Kind Regards, Simon Stelling Gentoo/AMD64 -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
Simon Stelling wrote: Even better: Fix them to use ~/.config/app instead, so they don't clutter up the home unnecessarily :) Won't it change how the vanilla upstream version and the one from portage behave? IMHO such changes are not a good idea. -- Krzysiek Pawlik nelchael at gentoo.org key id: 0xBC51 desktop-misc, desktop-dock, x86, java, apache, ppc... signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] About testing applications
Hi, Won't that break configs/increase clutter for people who share their home directories between two distributions since they'll have to restort to symlinks to make stuff work? I myself have gentoo and ubuntu installed and am sharing my home directory between them. I have to use ubuntu for maintaining a couple of packages and I can't live without gentoo :) On 3/18/07, Simon Stelling [EMAIL PROTECTED] wrote: Petteri Räty wrote: Many applications save preferences in ~/.app/. When testing applications please make sure you test with an empty directory to catch cases when an upgrade works fine but a clean install doesn't. Thanks. Even better: Fix them to use ~/.config/app instead, so they don't clutter up the home unnecessarily :) -- Kind Regards, Simon Stelling Gentoo/AMD64 -- gentoo-dev@gentoo.org mailing list -- Nirbheek Chauhan Sophomore UG Civil Engg ... -- Nirbheek Chauhan
Re: [gentoo-dev] About testing applications
Krzysiek Pawlik kirjoitti: Simon Stelling wrote: Even better: Fix them to use ~/.config/app instead, so they don't clutter up the home unnecessarily :) Won't it change how the vanilla upstream version and the one from portage behave? IMHO such changes are not a good idea. Just send the patch upstream and only apply it after upstream accepts it. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] About testing applications
On 18/03/07, Nirbheek Chauhan [EMAIL PROTECTED] wrote: Hi, Won't that break configs/increase clutter for people who share their home directories between two distributions since they'll have to restort to symlinks to make stuff work? I myself have gentoo and ubuntu installed and am sharing my home directory between them. I have to use ubuntu for maintaining a couple of packages and I can't live without gentoo :) Yes it would. Also, files beginning with . are not shown unless you use the -A/-a flag and therefore the traditional place for them is ~. Although having a ~/.config directory might make ~ look a bit cleaner, the use of .app directories instead of .app files, which is usual these days, helps to minimize the clutter. Also, if you have a .config directory to put all these files in, ~ becomes less cluttered but ~/.config becomes VERY cluttered! Jeff. -- Q: What will happen in the Aftermath? A: Impossible to tell, since we're still in the Beforemath. http://latedeveloper.org.uk -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
On 2007/03/18, Simon Stelling [EMAIL PROTECTED] wrote:
Even better: Fix them to use ~/.config/app instead
You mean ${XDG_CONFIG_HOME:-${HOME}/.config}/app, right?
http://standards.freedesktop.org/basedir-spec/latest/ar01s03.html
--
TGL.
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
On Sunday 18 of March 2007 13:37:55 Jeff Rollin wrote: Also, if you have a .config directory to put all these files in, ~ becomes less cluttered but ~/.config becomes VERY cluttered! Nothing prevents from making appdirs in .config too. -- Best Regards, Piotr Jaroszyński -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Last rites: www-servers/ncsa-httpd and net-im/aim-transport
# Raúl Porcel armin76 at gentoo dot org (18 Mar 2007) # Pending removal 17 May 2007, for treecleaners # www-servers/ncsa-httpd - bug 122134 # net-im/aim-transport - bug 145858 www-servers/ncsa-httpd net-im/aim-transport -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Firefox 1.5 series will get removed in 30 days
Hi, The mozilla team has decided that the www-client/mozilla-firefox[-bin]-1.5* series will get masked two weeks from now (18 Mar 2007), that is 1 April 2007. And will be removed after two weeks from that date, which will be 15 April 2007. Mozilla will drop support for that series from 24 April 2007 onwards. All arches have 2.0 series stable, so if you're using 1.5 you should migrate to 2.0. @GWN: Please include this in the next GWN. P.S: No, this is not an April fools joke :) Thanks. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Firefox 1.5 series will get removed in 30 days
Raúl Porcel kirjoitti: Hi, The mozilla team has decided that the www-client/mozilla-firefox[-bin]-1.5* series will get masked two weeks from now (18 Mar 2007), that is *1 April 2007*. *And will be removed after two weeks from that date*, which will be *15 April 2007*. Shouldn't an application as important as Firefox should get the usual month in package.mask? Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Firefox 1.5 series will get removed in 30 days
Petteri Räty wrote: Raúl Porcel kirjoitti: Hi, The mozilla team has decided that the www-client/mozilla-firefox[-bin]-1.5* series will get masked two weeks from now (18 Mar 2007), that is *1 April 2007*. *And will be removed after two weeks from that date*, which will be *15 April 2007*. Shouldn't an application as important as Firefox should get the usual month in package.mask? It's not the whole package, just older versions. With most packages, you wouldn't get the notification beforehand that older versions were disappearing. -- Andrew Gaffneyhttp://dev.gentoo.org/~agaffney/ Gentoo Linux Developer Installer Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Firefox 1.5 series will get removed in 30 days
Andrew Gaffney kirjoitti: Petteri Räty wrote: Raúl Porcel kirjoitti: Hi, The mozilla team has decided that the www-client/mozilla-firefox[-bin]-1.5* series will get masked two weeks from now (18 Mar 2007), that is *1 April 2007*. *And will be removed after two weeks from that date*, which will be *15 April 2007*. Shouldn't an application as important as Firefox should get the usual month in package.mask? It's not the whole package, just older versions. With most packages, you wouldn't get the notification beforehand that older versions were disappearing. Good point. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] dont use `which` in ebuilds
On Friday 16 March 2007, Petteri Räty wrote: Ned Ludd wrote: Here are the remaining offenders for sync 1174037821 that match '$(which ' or '`which ' in eclasses and ebuilds. dev-db/hsqldb/hsqldb-1.7.3.1-r1.ebuild:48: This one just echos which to a script so it's safe I think. The reasons why not to use which still apply. Even though which is used in a script instead of the ebuild itself. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net pgpY9jyEZ0nad.pgp Description: PGP signature
Re: [gentoo-dev] Firefox 1.5 series will get removed in 30 days
Petteri Räty wrote: Raúl Porcel kirjoitti: Hi, The mozilla team has decided that the www-client/mozilla-firefox[-bin]-1.5* series will get masked two weeks from now (18 Mar 2007), that is *1 April 2007*. *And will be removed after two weeks from that date*, which will be *15 April 2007*. Shouldn't an application as important as Firefox should get the usual month in package.mask? Regards, Petteri Ah, you want all the package masked? :P -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
On 18/03/07, Piotr Jaroszyński [EMAIL PROTECTED] wrote: On Sunday 18 of March 2007 13:37:55 Jeff Rollin wrote: Also, if you have a .config directory to put all these files in, ~ becomes less cluttered but ~/.config becomes VERY cluttered! Nothing prevents from making appdirs in .config too. True, but then .config would just become cluttered with .appdirs instead! -- Q: What will happen in the Aftermath? A: Impossible to tell, since we're still in the Beforemath. http://latedeveloper.org.uk
Re: [gentoo-dev] About testing applications
Jeff Rollin napsal(a): On 18/03/07, Piotr Jaroszyński [EMAIL PROTECTED] wrote: On Sunday 18 of March 2007 13:37:55 Jeff Rollin wrote: Also, if you have a .config directory to put all these files in, ~ becomes less cluttered but ~/.config becomes VERY cluttered! Nothing prevents from making appdirs in .config too. True, but then .config would just become cluttered with .appdirs instead! It wouldn't become any more or less cluttered than ~/ now... -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;) signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Firefox 1.5 series will get removed in 30 days
Sorry for sending the mail in HTML :) It won't happen again. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
On 18/03/07, Jakub Moc [EMAIL PROTECTED] wrote: Jeff Rollin napsal(a): On 18/03/07, Piotr Jaroszyński [EMAIL PROTECTED] wrote: On Sunday 18 of March 2007 13:37:55 Jeff Rollin wrote: Also, if you have a .config directory to put all these files in, ~ becomes less cluttered but ~/.config becomes VERY cluttered! Nothing prevents from making appdirs in .config too. True, but then .config would just become cluttered with .appdirs instead! It wouldn't become any more or less cluttered than ~/ now... Which is why I was saying there was no point in a ~/.config directory... Jeff -- Q: What will happen in the Aftermath? A: Impossible to tell, since we're still in the Beforemath. http://latedeveloper.org.uk
Re: [gentoo-dev] About testing applications
On Sun, 18 Mar 2007 21:46:40 + Jeff Rollin [EMAIL PROTECTED] wrote: Which is why I was saying there was no point in a ~/.config directory... Generally speaking one lists the contents of one's home directory more often than one lists ~/.config. It moves the clutter to a place where it's not so noticeable, and is thus a good thing. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] About testing applications
Jeff Rollin napsal(a): On 18/03/07, Jakub Moc [EMAIL PROTECTED] wrote: It wouldn't become any more or less cluttered than ~/ now... Which is why I was saying there was no point in a ~/.config directory... I guess you are missing the point? Fire up Midnight Commander and watch the cruft in your ~/; sure there'd be a point to move all these config files to a dedicated directory, instead of having them directly in ~/ (and no, I don't want to hide 'hidden' directories, this is not a Windows Explorer :P) -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;) signature.asc Description: OpenPGP digital signature
[gentoo-dev] text-markup hydra has born two new heads: sgml and tex
Hi everyone, as announced some time ago on this list, the text-markup herd has been split in two different herds: sgml, which will deal with (surprisingly) sgml and docbook packages, and tex for (La)TeX packages. An arbitrary decision of herding general text and OCR packages under tex has also been taken. Only one package has been left orphaned, and it's net-libs/libwww, which had arguably nothing to do in text-markup to begin with. Please, net-* people, don't leave the poor thing alone, especially since it has a tendency to grow security issues every now and then. The new herds have been created but the old one is not yet removed, I guess this will come in a while when we're sure nothing has been left out. Bugs have been reassigned and metadata.xml have been changed, but please signal any remaining sign of text-markup. Also, both of these herds are heavily understaffed, so any help would be much appreciated. Thanks for your attention, you can resume your daily activities. Regards, /Alexandre -- Hi, I'm a .signature virus! Please copy me in your ~/.signature. pgppBvvP2Gx0B.pgp Description: PGP signature
Re: [gentoo-dev] My turn to wear the cursed medalion of retirement
Hi Alexandre, Good luck in your new life. My only comment is that I think you copped out by not submitting your proposals for any sort of peer review. You succumbed to the possibility (that you seem to think is more of a probability -- you may be right, I don't know) that it would not be received well. I think it's a shame to succumb to such a fear (or any fear), and I wish you hadn't. I do understand where you're coming from, however, and I tend to agree with most of your ideas on the addition of bureaucratic layers and rules regulations. I struggle with whether or not that's simply a necessary by-product of the size and scope (I use the term loosely) of the project. Thanks, Seemant signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] moving USE=server to global
Mike Frysinger wrote: On Saturday 17 March 2007, Steve Long wrote: Piotr Jaroszy?ski wrote: I have heard about the magic limit of 5, but whatever... Is there a *technical* objection then to server? if you're going to change the topic mid-thread, then you should update the subject you already know the state of the server/client debate ... moving it to global doesnt fix any of the short comings, so it should stay local (and removed where possible) -mike Yeah -- server is way too generic. I've forgotten where else I use it, but when I build vnc I use it to get a VNC server. Maybe make a local vnc-server USE flag for that one. -- M. Edward (Ed) Borasky, FBG, AB, PTA, PGS, MS, MNLP, NST, ACMC(P) http://borasky-research.blogspot.com/ If God had meant for carrots to be eaten cooked, He would have given rabbits fire. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] My turn to wear the cursed medalion of retirement
Hi Alexandre. I too would like to hear what your ideas are for the metastructure of gentoo. Please if you dont feel up to officially submitting them then at least submit them to this list. Alistair On 3/19/07, Seemant Kulleen [EMAIL PROTECTED] wrote: Hi Alexandre, Good luck in your new life. My only comment is that I think you copped out by not submitting your proposals for any sort of peer review. You succumbed to the possibility (that you seem to think is more of a probability -- you may be right, I don't know) that it would not be received well. I think it's a shame to succumb to such a fear (or any fear), and I wish you hadn't. I do understand where you're coming from, however, and I tend to agree with most of your ideas on the addition of bureaucratic layers and rules regulations. I struggle with whether or not that's simply a necessary by-product of the size and scope (I use the term loosely) of the project. Thanks, Seemant
Re: [gentoo-dev] Why I don't think the CoC is a good idea
On Wednesday 14 March 2007, Alexandre Buisse wrote: The answer to that remark, and it has already been done in today's discussions, is that we should follow the spirit of the law and not its letter. But then, why do we need a Code of Conduct at all? There is nothing in it that people don't already know and if they choose to still commit the offense, it's either that they don't think it's one or that they choose to ignore the consequences and commit it anyway. In both cases, having a written code won't change a thing. sure it does ... if you dont outline consequences, how can there be any ? the spirit lives on; dont be an asshat and there's nothing for you to worry about ... if you start being being offensive, then you get tied down in rules I think that everyone should be free to participate in any discussion as long as some outrageous behaviours like racism are not shown and that the discussion stays on topic. But forcing people to not flame (and how does one define that anyway?) is simply an unnecessary freedom restriction. Great ideas can come from heated discussions, which can even be considered as a sign of good health, since people care enough to defend their ideas with passion. Or sometimes it is just funny, even if not everyone gets it. As long as one doesn't have to participate to this discussion, I don't see any problem. there's a difference between a heated discussion and flaming ... lumping the two together as being inseparable is wrong So my solution would be to just let things go as they currently are. If people want to make asses of themselves in public, great, let them do just that. If you don't like someone else, just don't read what they post. But if you freely choose to participate to a flame, live with the consequences, including the possibility of being called names by someone else (I don't know if there is an english equivalent, but a french saying goes like : it's a gourmet delice to be called an asshole by an idiot) and don't complain afterwards about it, because by acknowledging the very existence of the trolls, you fed them and gave them a target. we've tried this in the past and the only real thing we have to show for it are people leaving and offers of support withdrawn -mike pgpOM0zvbrglJ.pgp Description: PGP signature
Re: [gentoo-portage-dev] Add a couple new warnings to QA check
Ryan Hill wrote: Hey all. I'd like to add two warnings to the QA GCC warning message reporter for GCC 4.2. The first is a new warning that is given when GCC makes an optimization assuming that overflow for operations on signed ints is undefined, as per the standard. Apparently a lot of code assumes that it will wrap instead. The reason for this warning is the new -fstrict-overflow flag that is enabled at = -O2. The warning will only appear with the -Wstrict-overflow flag set, but it is enabled by -Wall so it will be seen pretty often. The other is actually a warning already present in =4.1. 4.2 now forbids function casts and will actually generate a runtime abort in the code if they're used. This is bad because the code will compile fine but then segfault when executed :(. openssl is a good example (bug #158324). This warning is always reported, even without -Wall. I hope this check will help identify packages that might not be GCC 4.2 ready. If you expect these warnings to be *fixed* by developers please provide documentation to enable developers to do so. SpanKY has some docs in trunk/doc/ for this express purpose. As much as I love QA checks I really don't like forcing them on people (doubly so for a failure mode check like this) without giving people advice on how to fix them. Thanks, -Alec -- gentoo-portage-dev@gentoo.org mailing list
