1 |
On Sun, 24 Apr 2011 17:29:29 -0500 |
2 |
William Hubbs <williamh@g.o> wrote: |
3 |
|
4 |
> On Sun, Apr 24, 2011 at 09:36:30AM +0200, Michał Górny wrote: |
5 |
> > The number of packages coming with systemd units is growing rapidly |
6 |
> > recently, and that especially applies to freedesktop packages. |
7 |
> > One side effect of that is that these packages treat systemd |
8 |
> > as an automagic dependency, installing systemd units whenever its |
9 |
> > pkgconfig file is installed. I already opened two bugs on that [2,3] |
10 |
> > but there would be much more... |
11 |
> > |
12 |
> > That's why I'm asking now: how should we proceed with installing |
13 |
> > systemd units? |
14 |
> > |
15 |
> > My current concept of keeping them separate from gx86 packages is |
16 |
> > good for a short early testing period but is a maintenance PITA for |
17 |
> > a longer term. And requires either adding |
18 |
> > '--without-systemdsystemunitdir' to a growing number of packages or |
19 |
> > removing the systemd.pc file (to avoid unit collisions). |
20 |
> |
21 |
> Where is the --without-systemdsystemunitdir option coming from? Is |
22 |
> that an option that is being provided by the packages or are you |
23 |
> providing it some how? |
24 |
|
25 |
It's provided by packages (and officially suggested by upstream). It |
26 |
works like that: |
27 |
1) if --without-systemdsystemunitdir is provided, systemd units are not |
28 |
installed, |
29 |
2) if --with-systemdsystemunitdir=... is provided, systemd units are |
30 |
installed in specified directory, |
31 |
3) if none of the above is provided, systemd checks for its pkgconfig |
32 |
file and grabs the directory from there. |
33 |
|
34 |
-- |
35 |
Best regards, |
36 |
Michał Górny |