On Wed, Apr 08, 2015 at 03:11:55PM +0200, Przemyslaw Kedzierski wrote: > On 04/07/2015 07:02 PM, Zbigniew Jędrzejewski-Szmek wrote: > >On Tue, Apr 07, 2015 at 12:36:31PM -0400, Rahul Sundaram wrote: > > >>Perhaps packaging guidelines should recommend running this command or it > >>should be part of the macro that packages include that logs warnings when > >>unit files has any of these issues > > > > We are interested in a tool that could be run automatically, > like rpmlint, at finish of build process. OK, I guess I wasn't clear: current systemd-analyze verify can be run automatically, but the output cannot be used to automatically reject a unit.
> It could read and check unit files from one service alone or in > context of all of them. This should be controlled by options. > There will be defined a set of rules, for both methods > Of course should be configurable the source of unit files used to > build a graph - currently installed in build system, from other > rpm's, > maybe from image? (what to do if target systemd will be too new than > running on build system) > > Is there only possible to check typos and syntax errors in case of > testing single unit file? > For example, problems like these: > http://lists.freedesktop.org/archives/systemd-devel/2011-March/001800.html Not currently, but I'm sure this could be added without much hassle. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
