Module submission - bmon

[Guillaume]

Le Fri, 8 Jun 2007 15:43:51 +0200,
Zbigniew Luszpinski <zbiggy at o2.pl> a écrit :
> Friday 08 of June 2007 03:31:02 Kok, Auke wrote:
> > sirocco at gmx.fr wrote:
> > > module name       : bmon
> > > suggested section : net
> > > update (y/n)      : n
> > > bugfix (y/n)      : y
> > > security (y/n)    : n
> > >
> > > Hello, since I've updated to gcc 4.1, some modules doesn't lin.
> > > bmon it one of theses. Here is a patch to make it lin correctly.
> > >
> > > I've not tested it with gcc 3.4 but it should works. I think it's a
> > > typo error (I'm not C/C++ specialist) some "=" are missing, that's
> > > what gcc told me, and it was right ;)
> >
> > that's indeed a big error and BAD typo to make
> >
> > the question is however: we should not keep silly patches like this - this
> > needs to go straight to the maintainer instead, and he should fix &&
> > release this immediately
> >
> > So, please try to do this first. Patch files are technically not allowed
> > inside moonbase, so this already needs work for a lunar dev (upload it, add
> > a download URL etc...)
> 
> Guillaume,
> I bypass the need of giving patch to Lunar developers by using sed (sedit) 
> inside build script to avoid .patch files. A little bit harder to do but 
> allows me to skip blessing from developers running Lunar's ftp and commit 
> update fast. I understand Auke's idealistic point of view but find it 
> sometimes too strict or impossible to do by average user. Users usually can 
> not push on application developer so hard to make him/her release fixed app 
> in less than 24h.
> 
> Auke has right. The developer of application should be informed about every 
> bug encountered. Making patch for Lunar do not release you from informing 
> application author because someone else using other distro will get trapped.
> The Linux users used to help each other - this helps survive whole community.
> Filling a bug report and adding patch to it on application's bugzilla is such 
> help to others. However we have to keep Lunar young, fresh and running 
> without waiting. This is the reason for adding patches till official app will 
> get fixed.
> If I make any patch to module I always send it to application developer too.
> Thanks to this later releases are get fixed by author so patches to lunar 
> becomes obsolete in later module updates.

Auke, zbiggy,
Ok, I'll have a look at sed.
I've sent the patch to bmon's author, but I also sent it to lunar because bmon
hasn't been updated for 2 years. There are a 2.1.1-pre1 and 2.2.0-pre1
version (05/2005) with the same errors, so I don't know if this software is still
maintained.

Guillaume