Re: [Lcd4linux-devel] this and that

[Xavier V. <xav...@fr...>]

Hello list

> >>I don't think a seperation in 'hard' and 'soft' does make sense...
> What do you mean by 'hard' and 'soft' (Depends, Recommends and Suggests?)?

#debian-devel-fr folks suggested to have a lcd4linux-drivers-hard (for
 real displays, with no external dep) and lcd4linux-drivers-soft (for
 X11,ncurses, ... so extern dep), but I don't think mayself it's good.

> >>Plugins with external dependencies: one .deb for every plugin ?
> >>Drivers with external dependencies: one .deb for each driver ?
> Definitely not, unless you only ever want a few plugins/drivers.
Markus suggested to have theme-based plugins :
lcd4linux-plugins-multimedia (xmms, others)
lcd4linux-plugins-system (i2c, cpu, mem, ...)
lcd4linux-drivers (hardware drivers)
lcd4linux-ncurses
lcd4linux-X11 (maybe both in the same deb ?)
lcd4linux-gnome-applet 
...

> > I really don't know what to do about this :/
> > Packaging non-dep plugins into lcd4linux package is a good idea. If
> > extern-deps plugins are not numerous we may think about making
> > one-plugin debs.
> Possible, another solution would be to Recommend the 'extern-deps' and 
> document the use of the dependencies in the extended description (so 
> everything is in one package).
I think it may be the better choice.

> How compares lcd4linux with lcdproc 
> (http://packages.debian.org/unstable/utils/lcdproc)?
I fact, lcdproc works with a networked server-client model : there's  
 LCDd, the server which cares of display and manages a network port,
  and multiple client (like lcdproc) which retrieve information, but I
 don't think lcdproc uses extern libraries.
OTOH, LCDd uses libncurses and I think it's a dep.

Bye !
-- 
Xavier VELLO <xav...@fr...>