Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-project
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-project@g.o
From: George Prowse <cokehabit@...>
Subject: Re: Improving developer/user communication
Date: Sat, 21 Jul 2007 12:00:11 +0100
Marijn Schouten (hkBst) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> George Prowse wrote:
>> Well, i'm not sure if this list is working because I have not yet
>> recieved any emails from it but...
>>
>> What ideas do people have for improving relations?
> 
> I posted twice to the list already, but nobody seems to have received it and I
> can't find it in the archive. Apologies to anyone receving this again.
> 
> first:
> 
> Robert Buchholz wrote:
>>> On Thursday, 19. July 2007 22:39, Jeroen Roovers wrote:
>>>>>>> Marijn Schouten (hkBst) wrote:
>>>>>>>>> Associate an irc-channel with each package.
>>>>> Associate how? Sounds like a lot of work at the least and a lot of
>>>>> cruft at the worst.
>>> It could be included in the herds.xml:
>>>
>>> <herd>
>>>   <name>kde</name>
>>>   <email>kde@g.o</email>
>>>   <description>KDE and related packages</description>
>>>   <irc>irc://irc.freenode.net/#gentoo-kde</irc>
>>>   <irc>irc://irc.freenode.net/#gentoo-desktop</irc>
>>>   <maintainer>
>>>     <email>caleb@g.o</email>
>>>   </maintainer>
>>>   ...
>>> </herd>
>>>
>>> This way, it would not cruft any packages. Still for packages where a
>>> certain group of people maintain, it would show where to find them and
>>> other users.
>>>
>>> Where could it be displayed to users? I mean, herdstat of course, but
>>> somehow the info would have to reach Joe User, too.
> 
> I was thinking of including it in the info that is spit out when you search
> for a package, for example:
> 
> eix -e pidgin
> * net-im/pidgin (#gentoo-pidgin, #gentoo-desktop)
>      Available versions:  (~)2.0.0 (~)2.0.1 (~)2.0.2 {avahi bonjour cjk crypt
> dbus debug doc eds gadu gnutls groupwise gstreamer gtk krb4 meanwhile msn
> ncurses networkmanager nls perl prediction qq sasl silc spell ssl
> startup-notification tcl tk xscreensaver zephyr}
>      Homepage:            http://pidgin.im/
>      Description:         GTK Instant Messenger client
> 
> Marijn
> 
> second:
> 
> Marijn Schouten (hkBst) wrote:
>>> Robert Buchholz wrote:
>>>>> Where could it be displayed to users? I mean, herdstat of course, but
>>>>> somehow the info would have to reach Joe User, too.
>>> I was thinking of including it in the info that is spit out when you search
>>> for a package, for example:
>>>
>>> eix -e pidgin
>>> * net-im/pidgin (#gentoo-pidgin, #gentoo-desktop)
>>>      Available versions:  (~)2.0.0 (~)2.0.1 (~)2.0.2 {avahi bonjour cjk crypt
>>> dbus debug doc eds gadu gnutls groupwise gstreamer gtk krb4 meanwhile msn
>>> ncurses networkmanager nls perl prediction qq sasl silc spell ssl
>>> startup-notification tcl tk xscreensaver zephyr}
>>>      Homepage:            http://pidgin.im/
>>>      Description:         GTK Instant Messenger client
>>>
>>> Marijn
> 
> Oh and in emerge failure messages:
> 
> collect2: ld returned 1 exit status
> make[2]: ***
> [/var/tmp/portage/sys-libs/glibc-2.6/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld.so]
> Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/sys-libs/glibc-2.6/work/glibc-2.6/elf'
> make[1]: *** [elf/subdir_lib] Error 2
> make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.6/work/glibc-2.6'
> make: *** [all] Error 2
>  *
>  * ERROR: sys-libs/glibc-2.6 failed.
>  * Call stack:
>  *   ebuild.sh, line 1647:   Called dyn_compile
>  *   ebuild.sh, line 988:   Called qa_call 'src_compile'
>  *   ebuild.sh, line 44:   Called src_compile
>  *   glibc-2.6.ebuild, line 1168:   Called src_compile
>  *   glibc-2.6.ebuild, line 1179:   Called toolchain-glibc_src_compile
>  *   glibc-2.6.ebuild, line 275:   Called die
>  *
>  * make for x86 failed
>  * Support in #gentoo-system or else #gentoo.
>  * Complete build log: '/var/tmp/portage/sys-libs/glibc-2.6/temp/build.log'.
> 
> with optional " or else #gentoo".
> 
> Marijn
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.5 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGocG7p/VmCx0OL2wRAlreAKDAhHyoEMb05GCD8zMCgUr2StnHYACghPFT
> lVc349FsckgxX1Hgg3Fwe4E=
> =VnFO
> -----END PGP SIGNATURE-----

I think that is a great idea, it would have the added effect of cutting
out some duplicated bug reports if people checked on #irc first.

>From a developer's side it may be a bit of a chore sometimes, especially
for those developers maintaining packages that are part of a herd that
they are not a member of.

-- 
gentoo-project@g.o mailing list


References:
Improving developer/user communication
-- George Prowse
Re: Improving developer/user communication
-- Marijn Schouten (hkBst)
Navigation:
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Improving developer/user communication
Next by thread:
Re: Improving developer/user communication
Previous by date:
Re: [Fwd: Reply to setting Was: Improving developer/user communication]
Next by date:
Re: Improving developer/user communication


Updated Jun 17, 2009

Summary: Archive of the gentoo-project mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.