Source: efl
Section: libs
Priority: optional
Maintainer: linuxmangaka <linuxmangaka@gmail.com>
Rules-Requires-Root: no
Build-Depends: debhelper-compat (= 13),
 ccache,
 clang,
 cmake,
 dpkg-dev,
 eject,
 gnulib,
 intltool,
 libavif-dev,
 libblkid-dev [linux-any],
 libc6-dev,
 libcurl4-openssl-dev,
 libdbus-1-dev,
 libedje-bin <cross>,
 libeet-bin <cross>,
 libefl-all-dev,
 libelementary-bin <cross>,
 libeolian-bin <cross>,
 libfontconfig-dev,
 libfreetype-dev,
 libfribidi-dev,
 libgbm-dev,
 libgdk-pixbuf-2.0-dev,
 libgcrypt-dev,
 libgif-dev,
 libgles2-mesa-dev,
 libglib2.0-dev,
 libgstreamer-plugins-base1.0-dev,
 libgstreamer1.0-dev,
 libharfbuzz-dev,
 libheif-dev,
 libinput-dev,
 libjack-jackd2-dev,
 libjpeg62-turbo-dev | libjpeg-turbo8-dev,
 libjpeg-dev,
 libjxl-dev,
 liblua5.1-dev,
 liblz4-dev,
 libmount-dev [linux-any],
 libopenjp2-7-dev,
 libpixman-1-dev,
 libpng-dev,
 libpoppler-cpp-dev,
 libpulse-dev,
 libraw-dev,
 librlottie-dev,
 librsvg2-dev,
 libscim-dev,
 libsndfile-dev,
 libspectre-dev,
 libssl-dev,
 libsystemd-dev,
 libtiff-dev,
 libudev-dev [linux-any],
 libunibreak-dev,
 libunwind-dev [amd64 arm64 armel armhf hppa i386 ia64 mips mips64 mips64el mipsel powerpc powerpcspe ppc64 ppc64el sh4],
 libvlc-dev,
 libwayland-dev,
 libwebp-dev,
 libx11-dev,
 libx11-xcb-dev,
 libxcb-image0-dev,
 libxcb-shm0-dev,
 libxcb1-dev,
 libxcomposite-dev,
 libxcursor-dev,
 libxdamage-dev,
 libxext-dev,
 libxi-dev,
 libxinerama-dev,
 libxkbcommon-x11-dev,
 libxpm-dev,
 libxrandr-dev,
 libxrender-dev,
 libxss-dev,
 libxtst-dev,
 mesa-common-dev,
 meson,
 ninja-build,
 pkgconf,
 pkg-config,
 systemd,
# systemd-dev,
 valgrind,
 wayland-protocols,
 x11proto-xext-dev,
 zlib1g-dev,
Build-Depends-Indep: doxygen <!nodoc>,
Build-Conflicts: systemctl,
Standards-Version: 4.6.2
Homepage: https://www.enlightenment.org/
Vcs-Browser: https://salsa.debian.org/pkg-e-team/efl
Vcs-Git: https://salsa.debian.org/pkg-e-team/efl.git

Package: libeina1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
X-Time64-Compat: libeina1a
Replaces: libeina1a,
Breaks: libecore-bin (<= ${source:Upstream-Version}),
 libedje-bin (<= ${source:Upstream-Version}),
 libeet-bin (<= ${source:Upstream-Version}),
 libeeze-bin (<= ${source:Upstream-Version}),
 libefreet-bin (<= ${source:Upstream-Version}),
 libeina-bin (<= ${source:Upstream-Version}),
 libeina1a (<< ${source:Version}),
 libelementary-bin (<= ${source:Upstream-Version}),
 libelementary-data (<= ${source:Upstream-Version}),
 libembryo-bin (<= ${source:Upstream-Version}),
 libeolian-bin (<= ${source:Upstream-Version}),
 libethumb-client-bin (<= ${source:Upstream-Version}),
 libevas-loaders (<= ${source:Upstream-Version}),
 libevas1-engines-drm (<= ${source:Upstream-Version}),
 libevas1-engines-fb (<= ${source:Upstream-Version}),
 libevas1-engines-wayland (<= ${source:Upstream-Version}),
 libevas1-engines-x (<= ${source:Upstream-Version}),
Conflicts: libeina0,
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

#Package: libeina1t64
#Architecture: linux-any
#Multi-Arch: same
#Pre-Depends: ${misc:Pre-Depends},
#Depends: ${shlibs:Depends},
# ${misc:Depends},
#Provides: ${t64:Provides},
#X-Time64-Compat: libeina1a
#Replaces: libeina1a,
#Breaks: libecore-bin (<= ${source:Upstream-Version}),
# libedje-bin (<= ${source:Upstream-Version}),
# libeet-bin (<= ${source:Upstream-Version}),
# libeeze-bin (<= ${source:Upstream-Version}),
# libefreet-bin (<= ${source:Upstream-Version}),
# libeina-bin (<= ${source:Upstream-Version}),
# libeina1a (<< ${source:Version}),
# libelementary-bin (<= ${source:Upstream-Version}),
# libelementary-data (<= ${source:Upstream-Version}),
# libembryo-bin (<= ${source:Upstream-Version}),
# libeolian-bin (<= ${source:Upstream-Version}),
# libethumb-client-bin (<= ${source:Upstream-Version}),
# libevas-loaders (<= ${source:Upstream-Version}),
# libevas1-engines-drm (<= ${source:Upstream-Version}),
# libevas1-engines-fb (<= ${source:Upstream-Version}),
# libevas1-engines-wayland (<= ${source:Upstream-Version}),
# libevas1-engines-x (<= ${source:Upstream-Version}),
#Conflicts: libeina0,
# libeina1,
#Description: EFL libraries
# EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeina-bin
Architecture: linux-any
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeet1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeet-bin
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libevas1-engines-x | libevas1-engine,
Recommends: libevas-loaders,
 libevas1-engines-drm,
 libevas1-engines-fb,
 libevas1-engines-wayland,
 libevas1-engines-x,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas1-engines-x
Architecture: linux-any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
Provides: libevas1-engine,
 libevas1-engine-gl-x11,
 libevas1-engine-software-x11,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas1-engines-fb
Architecture: linux-any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
Provides: libevas1-engine,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas1-engines-drm
Architecture: linux-any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
Provides: libevas1-engine,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas1-engines-wayland
Architecture: linux-any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
Provides: libevas1-engine,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-audio1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-con1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libecore-bin (>= ${source:Upstream-Version}),
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

#Package: libecore-con1t64
#Architecture: linux-any
#Multi-Arch: same
#Pre-Depends: ${misc:Pre-Depends},
#Depends: ${shlibs:Depends},
# ${misc:Depends},
# libecore-bin (>= ${source:Upstream-Version}),
#Provides: ${t64:Provides},
#Breaks: libecore-con1 (<< ${source:Version}),
# libeina1a (<< ${source:Upstream-Version}),
#Replaces: libecore-con1,
#Description: EFL libraries
# EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-drm2-1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-evas1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-fb1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-file1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-imf1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-input1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-ipc1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-wl2-1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-x1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libecore-bin
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libector1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libefl-all-dev
Section: libdevel
Architecture: linux-any
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libblkid-dev [linux-any],
 libcurl4-openssl-dev,
 libdbus-1-dev,
 libecore-audio1 (= ${binary:Version}),
 libecore-con1 (= ${binary:Version}) | libecore-con1t64 (= ${binary:Version}),
 libecore-drm2-1 (= ${binary:Version}),
 libecore-evas1 (= ${binary:Version}),
 libecore-fb1 (= ${binary:Version}) [linux-any],
 libecore-file1 (= ${binary:Version}),
 libecore-imf1 (= ${binary:Version}),
 libecore-input1 (= ${binary:Version}),
 libecore-ipc1 (= ${binary:Version}),
 libecore-wl2-1 (= ${binary:Version}),
 libecore-x1 (= ${binary:Version}),
 libecore1 (= ${binary:Version}),
 libector1 (= ${binary:Version}),
 libedje-bin (= ${binary:Version}),
 libedje1 (= ${binary:Version}),
 libeet1 (= ${binary:Version}),
 libeeze1 (= ${binary:Version}) [linux-any],
 libefreet1a (= ${binary:Version}),
 libeina1 (= ${binary:Version}) | libeina1t64 (= ${binary:Version}),
 libeio1 (= ${binary:Version}),
 libelementary1 (= ${binary:Version}),
 libelput1 (= ${binary:Version}),
 libembryo1 (= ${binary:Version}),
 libemile1 (= ${binary:Version}),
 libemotion1 (= ${binary:Version}),
 libeolian-bin (= ${binary:Version}),
 libeolian1 (= ${binary:Version}),
 libethumb-client1 (= ${binary:Version}),
 libethumb1 (= ${binary:Version}),
 libevas1 (= ${binary:Version}),
 libfontconfig-dev,
 libfreetype-dev,
 libfribidi-dev,
 libgbm-dev,
 libglib2.0-dev,
 libgstreamer-plugins-base1.0-dev,
 libgstreamer1.0-dev,
 libharfbuzz-dev,
 libinput-dev,
 libjpeg-dev,
 liblua5.1-dev,
 liblz4-dev,
 libmount-dev [linux-any],
 libpng-dev,
 libpulse-dev,
 libsndfile-dev,
 libssl-dev,
 libsystemd-dev,
 libudev-dev [linux-any],
 libunibreak-dev,
 libunwind-dev [amd64 arm64 armel armhf hppa i386 ia64 mips mips64 mips64el mipsel powerpc powerpcspe ppc64 ppc64el sh4],
 libwayland-dev,
 libx11-dev,
 libx11-xcb-dev,
 libxcb1-dev,
 libxcomposite-dev,
 libxcursor-dev,
 libxdamage-dev,
 libxext-dev,
 libxi-dev,
 libxinerama-dev,
 libxkbcommon-x11-dev,
 libxrandr-dev,
 libxrender-dev,
 libxss-dev,
 libxtst-dev,
 mesa-common-dev,
 pkgconf,
 python3,
 x11proto-xext-dev,
 zlib1g-dev,
 ${misc:Depends},
 ${shlibs:Depends},
Recommends: efl-doc,
 libeina-bin,
 libelementary-bin,
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libefreet1a
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libefreet-bin
Architecture: linux-any
Multi-arch: foreign
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libembryo1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Suggests: libembryo-bin,
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libembryo-bin
Section: devel
Architecture: linux-any
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libedje-bin
Section: devel
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libembryo-bin,
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libedje1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Suggests: libedje-bin (= ${binary:Version}),
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeio1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeeze1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeeze-bin
Architecture: linux-any
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libemile1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libemotion1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libethumb1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libethumb-client1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libethumb-client-bin
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeolian-bin
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libeolian1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libelput1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Breaks: libeina1a (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: efl-doc
Section: doc
Architecture: all
Multi-Arch: foreign
Build-Profiles: <!nodoc>
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libelementary1
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libelementary-data (= ${source:Version}),
Recommends: libelementary-bin,
Breaks: libeina1 (<< ${source:Upstream-Version}),
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libelementary-bin
Architecture: linux-any
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libelementary-data
Architecture: all
Multi-Arch: foreign
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.

Package: libevas-loaders
Architecture: linux-any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: EFL libraries
 EFL is a collection of libraries for handling many common tasks a developer may have such as data structures, communication, rendering, widgets and more. There are many components inside EFL. They also build various things like shared libraries, loadable plug-in modules and also binary executables. Different elements will end up being licensed differently too. Below is a rundown of the components, what they do and their licensing. All library source is in the src/lib/ directory. All binaries are in src/bin/. All loadable modules are in src/modules/. All data files are in the data/ directory. Licensing details are listed in COPYING and the licenses/ directory. The pc/ directory holds all the Package Config files installed to help developers build against EFL.