On Wed, 13 Jun 2012 14:30:58 +0100 Stefan Schmidt <[email protected]> said:
> Hello. > > We just had a short discussion on IRC about keeping or removing the HAL > backend used in E and EFM for the release. Main points seem to be: > > Arguments for removing: > - Mike as our main device backend guy does neither care nor use HAL. He > supports udisk and eeze mounting though. > - Keeping the code in for the release means we have to maintain it and > fix bugs. > - HAL upstream seems dead. > > Arguments for keeping: > - The BSD users still use it (There seem to be a udisk port for *BSD > http://ftp1.fr.freebsd.org/mirrors/rsync.frugalware.org/frugalware-stable/source/xapps/udisks/, > > any of our BSD users is using that) > > I there anything missing? I would like to hear back from people using a > recent (as in svn checkout) E with HAL and their reason. maintaining edbus hal means doing nothing - its protocol never changes. which is good. as for hal in e using edbu's shal api - yes, maintenance is needed, BUt we can remove it any time in future when no more hal installations exist, but bsd as you mention does so i think we are best off keeping it as hal has worked fine in the past and since hal is not a moving target, neither is support :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
