| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Building either dkms and non-dkms versions in one go is too hackish.
Moving the DKMS stuff on its own package (etherlab-ethercat-dkms).
|
|
The `-dkms` version of this package does not require building the kernel
modules, so handle that situation gracefully.
|
|
Now you have the option to install `etherlab-ethercat` (where the
modules are build for the current system) or `etherlab-ethercat-dkms`
(where the modules are rebuilt anytime the kernel changes).
The former approach (used originally before switching to DKMS) has
legitimate use cases, e.g. embedded systems where the kernel is not
supposed to change or where you have limited storage space.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The kernel modules are released with under the same license of the Linux
kernel while the user-space library is released under LGPL 2.1: see
`documentation/ethercat_doc.tex`, `License` section.
Furthermore, use proper SPDX ids (as suggested by the PKGBUILD wiki):
https://spdx.org/licenses/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
According to the official documentation [1]:
The downloaded source filename must be unique because the SRCDEST
directory can be the same for all packages.
[1] https://wiki.archlinux.org/title/PKGBUILD
|
|
From now on, there should be proper semantic versioning:
https://gitlab.com/etherlab.org/ethercat/-/issues/9
|
|
This includes the following changes:
- target newly introduced branch `stable-1.6`
- update to latest commit
- fix for linux kernel >= 6.9
|
|
Follow what suggested by VCS guidelines:
https://wiki.archlinux.org/title/VCS_package_guidelines
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|