gmodconfig-devel — Developers' mailing list

Re: [gmodconfig-devel] modgui.cpp - assert.h missing ?

[Cyril B. <bo...@us...>]

Alban Browaeys wrote:
> I had to include assert.h for gcc 3.3.1 to compile modgui.cpp
> 
> Great tool (from the site), let s go try it now !
> 
> Cheers
> Alban

OK, it's now fixed in CVS. Thanks for the report.

Cyril

[gmodconfig-devel] modgui.cpp - assert.h missing ?

[Alban B. <alb...@or...>]

I had to include assert.h for gcc 3.3.1 to compile modgui.cpp

Great tool (from the site), let s go try it now !

Cheers
Alban

[gmodconfig-devel] Using CLAN to install and build modules

[Cyril B. <bo...@us...>]

Building and installing new versions of modules, or new
modules easily is one of the goals of gmodconfig. I'm
thinking about using CLAN for this purpose:

http://fc-solve.berlios.de/CLAN/

Has anyone tried it before?

Cyril

[gmodconfig-devel] Using XSA to check for kernel modules updates

[Cyril B. <bo...@us...>]

One of the goals of gmodconfig is to let users check
if new versions of a kernel module are available.
That information would appear to the user in the
"Updates" tab (not yet implemented).

To achieve this, I'm thinking about using XSA:
http://www.garshol.priv.no/download/xsa/

Here's how it could work:
- A kernel module author creates an XSA file that
   contains informations about the latest release of
   his kernel module. I have a simple GUI in mind that
   I can add to gmodconfig.
- The author publishes this XSA file on a website and
   stores the URL to that file into the "module description"
   XML file (I'm referring here to the XML file that has
   parameter descriptions with translations etc... see for
   example ov511.xml in gmodconfig's tarball or in CVS).
- A user starts gmodconfig, clicks on a module, looks at
   the "Updates" tab. gmodconfig then retrieves the XSA file
   and displays the informations in the tab.
- When a new release is available, the kernel module author
   just updates the XSA file.

Any comments?

Cyril