Le Sat, 16 Mar 2002 16:09:28 +0100, Quel Qun a �crit :
> On Sat, 2002-03-16 at 06:33, Pascal Terjan wrote:
>> Quel Qun wrote:
>> >>
>> > Could someone make a simple rpmmon query javascript form on the
>> Mandrake web?
>>
>> Use rpmfind, select the first result from Mandrake, read the page with
>> rpm headers, then read the maintainer's name... Or, if you have the rpm
>> installed, you may use something like : rpm -q --queryformat
>> "%{packager}\n" packagename
>>
>>
> $ rpm -q --queryformat "%{packager}\n" xinitrc Mandrake Linux Team
> <http://www.mandrakeexpert.com>
>
> I assume the packager info is not available in the rpm packages, so I
> won't get more info if I manage to read the output of rpm2header
There is a difference between packager and maintainer :
-Maintainer is the guy who is in charge of day to day package
maintainance (bug fix, new version, ...)
-Packager is the last guy who built the package. If I rebuild package I
don't maintain (sometimes, it is needed because the maintainer is too
busy or we need to fix a lot of package at the same time), my name will
be put in the packager tag and some people might think I'm the maintainer
of the package (it happened with Mdk 8.0 for me with Samba because I
fixed menu entry for swat !!).
It wouldn't be a problem if people (very often, newbies) weren't sending
mail for tech support directly to packagers (or maintainers..)
That is why I'm (and a lot of people at MandrakeSoft) using the
"MandrakeExpert" tag => to redirect users to mandrakeexpert.com for tech
support. This is really needed for released version of the distro)
For cooker, the best thing is often to post on cooker mailing list.
Info is not restricted between Mdksoft guy and the guy sending
mail and it might help other people (or other people might be able to
respond to initial mail..)
Since cooker traffic is quite high, some mails might not be read by the
right MdkSoft guy (I confess, I usually don't read long OT threads or
install related threads..)..
To reduce this problem, I think people should try to split their mails by
package/topic (if in an install report, there is stuff about GNOME not starting,
chance are high it might be missed) and to put really good topics for
their messages.
Here is an example (inspired from a bug I received this week .. At first,
I thought it was already fixed but it was indeed a real bug ;)
bad topic : icons are not active on my desktop
good topic : [GNOME] desktop icons not working
or for gnome power users : [Nautilus] desktop icons not working
A good rule of thumb would be to put package name at the beginning of
topic..
--
Fr�d�ric Crozat
MandrakeSoft
