Yes in this case they probably should be on by default with a disable flag if someone doesn't want them. That makes it much easier for packagers to pick up there missing a dep
Cheers On 06/05/2016 06:18 PM, Tom Hacohen wrote: > Hm... we don't do "if dependencies are found" any more... This should be > reverted. > > The point of not having magic is not having magic. We want things to > explicitly fail when deps are missing. Not implicitly disabled. > > -- > Tom. > > On 04/06/16 20:45, Dave Andreoli wrote: >> davemds pushed a commit to branch master. >> >> http://git.enlightenment.org/core/efl.git/commit/?id=e21d357adf9b223659c4595bf4483a3111f44c65 >> >> commit e21d357adf9b223659c4595bf4483a3111f44c65 >> Author: Dave Andreoli <d...@gurumeditation.it> >> Date: Sat Jun 4 21:45:28 2016 +0200 >> >> Enable evas loaders by default, if dependencies are found >> >> I really cannot see why we should require to use --enable-feature on >> those, they should be safe. >> --- -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
