Examples of use
Defining package category
With ELIAS 18, eLux packages can be shown sorted by category. Assign a category to your custom packages.
- Edit the file /input/epkepm:
edit ./input/epkepm - For your packages, in the epm section, set the category parameter. Example:
[EPM]
category=Communication
The following categories can be set:
Category | Description | Example |
---|---|---|
System | Operating system components | eLux OS, Linux kernel, deskop environment |
Application | Back-end and local applications, web browsers | Citrix Workspace-App, VMware Horizon client, Firefox |
Security | VPN, smart card middleware | Cisco AnyConnect, cryptovision sc/interface |
Communication | Unified Communication, VoIP | Cisco JVDI, Citrix HDX RTME, Zoom Citrix plugin, Zoom client for Linux, Ekiga SoftPhone |
Network | Proxy, Network Access Control | Squid proxy server, IEEE802.1X |
Multimedia | Audio, Video | GStreamer, Fluendo Codec Pack |
Driver | Support for new hardware | WLAN, WWAN, printers |
Utility | Libraries | BIOS update, XInput Calibrator |
Miscellaneous | Custom packages, packages without category |
If you do not set a category for your package, the package will be displayed under Miscellaneous.
Converting a package tree structure to the meta file structure
-
To convert a package tree into the new meta format, use the following commands:
epkg NewFrom --pkgTree=<path to package tree>
All required files are created under elux/, but the files are empty.
-
Fill *.thirdparty and *.debs with the input data.
epkg ConvertFrom --pkgTree=<path to package tree> --container =rp6_x64 The *.install and *.dirs meta files are filled and the required folders are created under input/.
Building a package in test mode
epkg Build --releaseType=test --container=rp6_x64
The test mode is enabled by default.
Building a package in release mode
epkg Build --releaseType=release --container=rp6_x64
Building a package without signing and zipping
epkg Build --skipSign -–skipCreateZip --container=rp6_x64
Installing a package
epkg Install
All EPM/FPMs, the signature files and the ..zip file are copied to the configured container directory.