Gentoo Archives: gentoo-project

From: George Prowse <cokehabit@×××××.com>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Improving developer/user communication
Date: Sat, 21 Jul 2007 11:00:28
Message-Id: 46A1E73B.2030104@gmail.com
In Reply to: Re: [gentoo-project] Improving developer/user communication by "Marijn Schouten (hkBst)"
1 Marijn Schouten (hkBst) wrote:
2 > -----BEGIN PGP SIGNED MESSAGE-----
3 > Hash: SHA1
4 >
5 > George Prowse wrote:
6 >> Well, i'm not sure if this list is working because I have not yet
7 >> recieved any emails from it but...
8 >>
9 >> What ideas do people have for improving relations?
10 >
11 > I posted twice to the list already, but nobody seems to have received it and I
12 > can't find it in the archive. Apologies to anyone receving this again.
13 >
14 > first:
15 >
16 > Robert Buchholz wrote:
17 >>> On Thursday, 19. July 2007 22:39, Jeroen Roovers wrote:
18 >>>>>>> Marijn Schouten (hkBst) wrote:
19 >>>>>>>>> Associate an irc-channel with each package.
20 >>>>> Associate how? Sounds like a lot of work at the least and a lot of
21 >>>>> cruft at the worst.
22 >>> It could be included in the herds.xml:
23 >>>
24 >>> <herd>
25 >>> <name>kde</name>
26 >>> <email>kde@g.o</email>
27 >>> <description>KDE and related packages</description>
28 >>> <irc>irc://irc.freenode.net/#gentoo-kde</irc>
29 >>> <irc>irc://irc.freenode.net/#gentoo-desktop</irc>
30 >>> <maintainer>
31 >>> <email>caleb@g.o</email>
32 >>> </maintainer>
33 >>> ...
34 >>> </herd>
35 >>>
36 >>> This way, it would not cruft any packages. Still for packages where a
37 >>> certain group of people maintain, it would show where to find them and
38 >>> other users.
39 >>>
40 >>> Where could it be displayed to users? I mean, herdstat of course, but
41 >>> somehow the info would have to reach Joe User, too.
42 >
43 > I was thinking of including it in the info that is spit out when you search
44 > for a package, for example:
45 >
46 > eix -e pidgin
47 > * net-im/pidgin (#gentoo-pidgin, #gentoo-desktop)
48 > Available versions: (~)2.0.0 (~)2.0.1 (~)2.0.2 {avahi bonjour cjk crypt
49 > dbus debug doc eds gadu gnutls groupwise gstreamer gtk krb4 meanwhile msn
50 > ncurses networkmanager nls perl prediction qq sasl silc spell ssl
51 > startup-notification tcl tk xscreensaver zephyr}
52 > Homepage: http://pidgin.im/
53 > Description: GTK Instant Messenger client
54 >
55 > Marijn
56 >
57 > second:
58 >
59 > Marijn Schouten (hkBst) wrote:
60 >>> Robert Buchholz wrote:
61 >>>>> Where could it be displayed to users? I mean, herdstat of course, but
62 >>>>> somehow the info would have to reach Joe User, too.
63 >>> I was thinking of including it in the info that is spit out when you search
64 >>> for a package, for example:
65 >>>
66 >>> eix -e pidgin
67 >>> * net-im/pidgin (#gentoo-pidgin, #gentoo-desktop)
68 >>> Available versions: (~)2.0.0 (~)2.0.1 (~)2.0.2 {avahi bonjour cjk crypt
69 >>> dbus debug doc eds gadu gnutls groupwise gstreamer gtk krb4 meanwhile msn
70 >>> ncurses networkmanager nls perl prediction qq sasl silc spell ssl
71 >>> startup-notification tcl tk xscreensaver zephyr}
72 >>> Homepage: http://pidgin.im/
73 >>> Description: GTK Instant Messenger client
74 >>>
75 >>> Marijn
76 >
77 > Oh and in emerge failure messages:
78 >
79 > collect2: ld returned 1 exit status
80 > make[2]: ***
81 > [/var/tmp/portage/sys-libs/glibc-2.6/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld.so]
82 > Error 1
83 > make[2]: Leaving directory
84 > `/var/tmp/portage/sys-libs/glibc-2.6/work/glibc-2.6/elf'
85 > make[1]: *** [elf/subdir_lib] Error 2
86 > make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.6/work/glibc-2.6'
87 > make: *** [all] Error 2
88 > *
89 > * ERROR: sys-libs/glibc-2.6 failed.
90 > * Call stack:
91 > * ebuild.sh, line 1647: Called dyn_compile
92 > * ebuild.sh, line 988: Called qa_call 'src_compile'
93 > * ebuild.sh, line 44: Called src_compile
94 > * glibc-2.6.ebuild, line 1168: Called src_compile
95 > * glibc-2.6.ebuild, line 1179: Called toolchain-glibc_src_compile
96 > * glibc-2.6.ebuild, line 275: Called die
97 > *
98 > * make for x86 failed
99 > * Support in #gentoo-system or else #gentoo.
100 > * Complete build log: '/var/tmp/portage/sys-libs/glibc-2.6/temp/build.log'.
101 >
102 > with optional " or else #gentoo".
103 >
104 > Marijn
105 > -----BEGIN PGP SIGNATURE-----
106 > Version: GnuPG v2.0.5 (GNU/Linux)
107 > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
108 >
109 > iD8DBQFGocG7p/VmCx0OL2wRAlreAKDAhHyoEMb05GCD8zMCgUr2StnHYACghPFT
110 > lVc349FsckgxX1Hgg3Fwe4E=
111 > =VnFO
112 > -----END PGP SIGNATURE-----
113
114 I think that is a great idea, it would have the added effect of cutting
115 out some duplicated bug reports if people checked on #irc first.
116
117 >From a developer's side it may be a bit of a chore sometimes, especially
118 for those developers maintaining packages that are part of a herd that
119 they are not a member of.
120
121 --
122 gentoo-project@g.o mailing list