We need it keyworded in more arches due Gnome 3.8
I think this might be where these three architectures have to hop off the gnome train. I suspect it's going to be very difficult to keep up with systemd and its requirements.
Let's see what others think.
I really don't want these architectures to hold up gnome 3.8. Can we (perhaps temporarily) USE mask systemd and the bits of gnome that unconditionally depend on it and be safe?
I would really prefer if you could try to keyword it, if major problems appear in the future, you can drop the keyword then. What exact problems have systemd currently on your arches?
Alpha, HPPA, SH and everyone who doesn't support CONFIG_AUDITSYSCALL=y kernel feature should package.use.mask 'pam' for sys-apps/systemd as per:
As in, please don't forward port the bugs from CK handling over to systemd too
ia64 looks to have problems for this, but what is blocking sparc and ppc?
Keywords for sys-apps/systemd:
| | u |
| a a p s | n |
| l m h i m m p s p | u s | r
| p d a p a 6 i p c 3 a x | s l | e
| h 6 r p 6 8 p p 6 9 s r 8 | e o | p
| a 4 m a 4 k s c 4 0 h c 6 | d t | o
201 | o + + o o o o o + o o o + | # 0 | gentoo
204 | o + + o o o o + + o o o + | o | gentoo
206-r3 | o ~ ~ o o o o ~ ~ o o o ~ | o | gentoo
9999-r1 | o o o o o o o o o o o o o | o | gentoo
ppc is done
But looks like systemd USE flag is still masked on ppc
ppc done (after talking with Ago)
Can anyone from sparc and alpha team look at this? Thanks
i'll take a look at this for sparc as i can do run-time testing, i had to fix my cvs tree first. thanks
Would be nice if alpha and sparc (at least, since ia64 issue looks more complicated) could give this a higher priority :|
I spent some time this weekend trying to make systemd work on alpha (sorry for the long delays). The ebuild says I need CONFIG_SECCOMP, which isn't available on alpha.
I ran into a kernel panic that I need to work through, but once that's fixed I'll attempt to run systemd without SECCOMP.
(In reply to Matt Turner from comment #11)
> I ran into a kernel panic that I need to work through, but once that's fixed
> I'll attempt to run systemd without SECCOMP.
It will probably run, but there might be trouble with any units that utilize the SystemCallFilter parameter. systemd does not ship with any such units.
added ~alpha and removed systemd from use.mask. :)
Nice, thanks a lot :D
If anyone could look for this on sparc, would be nice (to not need to drop packages from gnome-3.8 stabilization list). Thanks