Le vendredi 27 juillet 2007 à 14:47 +0200, Arnaud Quette a écrit : > 2007/7/27, Philippe Normand <[EMAIL PROTECTED]>: > > Le jeudi 26 juillet 2007 à 19:16 +0200, Ouattara Oumar Aziz a écrit : > > > > Hi all ! > > > > > > Hi Loic, > > > > > > > > > > > > > > Create another plugin (reference to the meeting last night) to select > > > > your remote control from a list, and copy the right lircd.conf (with the > > > > new name space applied). With the lirc.hdwb, it can be very easy. There > > > > is just the problem that lircd.conf have the right place in /etc. So > > > > must some root privileges. If you have any suggestions for this and to > > > > create plugin. Wattazoum maybe you can help me for this point ? > > > > > > As for the plugin for selectioning the remote control from a list, it's > > > part of the UMC config GUI spec :-) . But the job of managing config > > > files, must be on the LIRC plugin side . > > > > > > I don't know much about LIRC, tell me if I understood well, there is > > > only one controller that can be configured at a time ? > > > > > > If it's the case and if we need to do this at the user level there is 2 > > > solutions I see : > > > - Implement a multicontroller feature in LIRC > > > - create a deamon that will be run at boot time ( so by the root user ) > > > and that will be listening at UMC request for changing the lircd.conf > > > file. > > > > > > I prefer the 1rst solution but it's a long term solution with lot of > > > work and Spec . > > > > > > The second one seems quite easy. > > > wattazoum > > > > The way I understand LIRC, you can't use more than one remote at a time, > > lircd.conf doesn't support that. > > right, multi driver instance implies multi lircd daemon (1 per driver...) > > http://lirc.org/html/configure.html#multiple > > > The daemon needs to be runned by the root user, we can't really cope > > with that. So every time lircd.conf is updated, lircd needs to be > > restarted, AFAIK > > same issue than handling the system shutdown from within elisa btw. > and that is somehow needed on dedicated system... > > > About the LIRC config plugin, the lirc elisa input_provider has its own > > config (like all components of Elisa). The most relevant option there is > > the .lirc filename which maps actual remote keys to elisa input_event > > "actions". Elisa will ship with various .lirc files (currently there's > > one for streamzap remote and one for the apple remote). Users are > > welcome to contribute their .lirc files, we can't buy all remotes of the > > market :) > > > > What's the deadline for all this config stuff? > > only the remote selection is needed urgently (for the Gutsy release).
Which means in terms of calendar? I read on the release schedule that FeatureFreeze is on August, 16th. Is that the actual deadline or am I misunderstanding completely that schedule? :) > and possibly the mandatory points to avoid editing elisa.conf, that is > for the media dirs. As I told just before the last meeting, Elisa now supports xdg-user-dirs which is implemented in Gustsy. Media selection within the config UI would probably still be needed, but having xdg-users-dir is a good start. > Are there any other mandatory things on the elisa side? > the complete config and installation GUIs will come later on. > > Still for the Gutsy release, we'll manage many things inside the UMC > repository... > > Arnaud
