Make device packages consistently use devicepkg-dev

Created by: ollieparanoid

Using devicepkg-dev is the modern way of creating device- aports. It can automatically generate udev rules for the touch screen (which works for most devices, if it does not, we can still add an extra udev rule on top of that, or ideally improve devicepkg-dev, that it also works for those devices).

It would be nice if all device packages used devicepkg-dev, so we have them consistent. To make sure that we don't have regressions, we would need to test each device after changing it. So if you own one of the devices on the list, you could help out with resolving this with the following steps:

copy your current device- aport to a temporary folder
run pmbootstrap aportgen device-CODENAME
adjust the newly generated aport, so it has the same features as the old-style one
test the new aport
when the functionallity is the same, please create a pull request and mention that you have tested that it works on the device.

These devices were built with an old template which does not have the # Reference: <https://postmarketos.org/devicepkg> line (and in most cases that means, they are not using devicepkg-dev either):

List generated with:

for i in $(grep -rL Reference aports/device/device-*/APKBUILD | cut -d / -f 3 | cut -d- -f 2- | sort); do echo " - [ ] $i"; done

Edited Aug 19, 2018 by Administrator

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information