| 1 |
We have two eclasses with almost-identical functions for handling |
| 2 |
tmpfiles.d entries: |
| 3 |
|
| 4 |
1. systemd.eclass |
| 5 |
|
| 6 |
a. systemd_dotmpfilesd |
| 7 |
b. systemd_newtmpfilesd |
| 8 |
c. systemd_tmpfiles_create |
| 9 |
|
| 10 |
2. tmpfiles.eclass |
| 11 |
|
| 12 |
a. dotmpfiles |
| 13 |
b. newtmpfiles |
| 14 |
c. tmpfiles_process |
| 15 |
|
| 16 |
The do/new functions are basically identical, while the create/process |
| 17 |
functions differ only in the fact that the one from tmpfiles.eclass |
| 18 |
supports opentmpfiles as well. Why do we have both? Couldn't the |
| 19 |
systemd.eclass ones be implemented in terms of the tmpfiles.eclass ones, |
| 20 |
and then deprecated (in favor of tmpfiles.eclass itself) in newer EAPIs? |
| 21 |
|
| 22 |
Or am I missing something? |
Archives