1 |
On 11/08/2016 10:44 PM, Daniel Campbell wrote: |
2 |
> On 11/08/2016 05:02 PM, Rich Freeman wrote: |
3 |
>> On Tue, Nov 8, 2016 at 7:54 PM, Patrick McLean <chutzpah@g.o> wrote: |
4 |
>>> On Tue, 8 Nov 2016 17:41:02 -0600 |
5 |
>>> William Hubbs <williamh@g.o> wrote: |
6 |
>>>> |
7 |
>>>> The plan, once the first release is out, is to rewrite this utility |
8 |
>>>> in a better language. I'm considering C, but if I am comfortable by |
9 |
>>>> that time in Go or Rust, I may use one of them. |
10 |
>>>> |
11 |
>>> |
12 |
>>> For a low-level utility that is likely going to be in the default |
13 |
>>> @system set, please use C. Adding dependencies on the go or rust |
14 |
>>> compilers for this is not very nice. |
15 |
>>> |
16 |
>> |
17 |
>> Assuming I'm looking at the right sources, the actual systemd |
18 |
>> implementation is only 2342 lines of C. Glancing at the includes, I'm |
19 |
>> not convinced it even requires systemd to run. |
20 |
>> |
21 |
>> You might want to take a look at either just creating a split ebuild, |
22 |
>> or tweaking it to work standalone if necessary. |
23 |
>> |
24 |
> Is that including any headers and/or libraries shared by the systemd |
25 |
> umbrella? |
26 |
> |
27 |
|
28 |
It has a huge list of includes for internal libraries, from acl-util.h |
29 |
to util.h: |
30 |
|
31 |
https://github.com/systemd/systemd/blob/master/src/tmpfiles/tmpfiles.c |
32 |
-- |
33 |
Thanks, |
34 |
Zac |