Commit Graph

5 Commits

Author SHA1 Message Date
Carsten Haitzler 5f47c52f7c e default config - disable more modules we don't really need
teamwork is a nice idea but really it's more of a vector for issues
asking e to pop up files or uri's via dbus from apps that are gui apps
that... can do this themselves anyway :)
2019-07-09 10:17:55 +01:00
Carsten Haitzler cf76bd8338 e config - dont have module loade delay as it is no longer useful
module lload delay was for the days of spinning hdd's AND before we
were compositing so we could have an init splash in x then load
modules in the bg while its up etc. ... no longer relevant so off.
2019-07-09 10:17:55 +01:00
Carsten Haitzler 933eb51e47 profile config - disable ibox as ibar does this these days anyway
pointless having both ibar and ibox, so let ibar do it by default
2019-07-09 10:17:55 +01:00
Carsten Haitzler 6cb62a79ae wizard - missing bluez5 service checks for enabling bluez5 module
we were missing this - add it in like connman for release.
2019-07-09 10:17:55 +01:00
Mike Blumenkrantz 05d3f2d393 move config/ to data/config/
Summary:
this is part of the datadir distribution, it should not be in a different
directory than the rest of the datadir distribution

the gnu coding standards (https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
define 'datadir' as:

The directory for installing idiosyncratic read-only architecture-independent
data files for this program. This is usually the same place as ‘datarootdir’,
but we use the two separate variables so that you can move these program-specific
files without altering the location for Info files, man pages, etc.

This should normally be /usr/local/share, but write it as $(datarootdir).
(If you are using Autoconf, write it as ‘@datadir@’.)

The definition of ‘datadir’ is the same for all packages, so you should install your
data in a subdirectory thereof. Most packages install their data under $(datadir)/package-name/.

while this text has no clear requirement or suggestion for a corresponding
repository layout, projects typically employ a certain consistency in their
repository layout both for ease of maintenance and ease of learning for new
contributors.

this project has both a data/ directory, which contains the datadir distribution,
as well as the config/ directory, which also contains the datadir distribution.
this complicates matters both for active maintainers/developers who must
remember that the repository and build tree layouts have this exception,
and for new contributors who will initially be confused by this exception

other well-organized open source projects, such as wayland, have chosen to not
use a data/ directory. these projects have the datadir distribution in the base
directory of the repositor, which is a fine practice as it maintains consistency
for the project since all the files for the datadir distribution are in the same
directory.

by applying this patch, the project will move towards a more easily readable and
learnable layout. current and future developers will no longer need to wonder why
this directory is outside of the data/ directory, and anyone attempting to reference
these files from the source/build trees will be able to do so more easily

ref D6013

Reviewers: cedric, raster, bu5hm4n

Reviewed By: raster

Subscribers: devilhorns

Tags: #enlightenment-git

Differential Revision: https://phab.enlightenment.org/D6154
2018-05-15 15:30:14 +02:00