<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 24 February 2015 at 20:48, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":329" class="a3s" style="overflow:hidden">I feel we are going out of way here since now on systemd based systemd you have to undo this change<br>
partly via re-introducing service files in some fashion<br>
how about just building and packaging uuidd and fstrim separately ?</div></blockquote></div><br></div><div class="gmail_extra">Well the question is how popular is uuidd and fstrim? I can totally see that installing the service files if systemd is enabled is the obvious half-way and upstream supporting this would be good but I've no idea if they'd accept this.</div><div class="gmail_extra"><br></div><div class="gmail_extra">We are *very* close to M3 cut-off and landing the new systemd depends on something fixing the circular dependency. I believe this patch is the path with the least impact that can be fixed post-M3 to install service files where appropriate without causing a circular build dependency.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>