Hi Tim > Well, actually i just created the libnih stuff for upstart?!?
You wrote udev in the header :-) Anyway - We're using upstart similar as on Ubuntu lucid for our ptxdist projects. For about 10 months or so. Talking about upstart, also means talking how these initmethods should be handled. The current way turned out to be difficult to maintain. > > Maybe I should get our server up and running again and publish my > > patches again. > Jep, good idea. I'm on holidays these days. But as we still use upstart 0.6.3. So I will pick up your patches when I'm back at work. You might want to check and possibly review the following topic branch for changes related to initmethod-upstart. Maybe you can save some duplicate work. Any feedback is welcome. http://git.vahanus.net/?p=csc/ptxdist-kp.git;a=shortlog;h=refs/heads/for-upstream-next If you want to compile a project with it, you probably need some hacked files for upstart from our projectroot/ - Mountall isn't working yet and replaced by some script hacking. > Btw. you are not by chance working on qt46 packages ;-). It would be nice to > join forces there too. Not yet, as we don't have any displays for our boxes yet. But this might change soon. Right now we focus on porting /etc/init/* scripts from Ubuntu and replace the classic rc.d links. I also need to rework the current initmethod-* implemenation -- all these rc.d, /etc/init or whatever files required for your selected initmethod should be selected/linked depending on information provided by the package targetinstall stage and .in options. Currently information is spread over several files. Otherwise the upstart stuff works really fine. We just prepared a new firmware using it. Although it still uses rc.d links for most packages it already saved several seconds on startup. -- Carsten Schlote <[email protected]> -- ptxdist mailing list [email protected]
