<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.4.3">
</HEAD>
<BODY>
El vie, 24-08-2012 a las 09:58 -0300, Nicolás Reynolds escribió:<BR>
<BLOCKQUOTE TYPE=CITE>
<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="1">
<TR>
<TD>
<FONT SIZE="2">mensaje de correo electrónico adjunto ([arch-dev-public] [RFC] systemd service files policy)</FONT>
</TD>
</TR>
</TABLE>
<BLOCKQUOTE TYPE=CITE>
--------- Mensaje reenviado --------<BR>
<B>De</B>: Tom Gundersen <<A HREF="mailto:Tom%20Gundersen%20%3cteg@jklm.no%3e">teg@jklm.no</A>><BR>
<B>Reply-to</B>: Public mailing list for Arch Linux development <arch-dev-public@archlinux.org><BR>
<B>Para</B>: Public mailing list for Arch Linux development <<A HREF="mailto:Public%20mailing%20list%20for%20Arch%20Linux%20development%20%3carch-dev-public@archlinux.org%3e">arch-dev-public@archlinux.org</A>><BR>
<B>Asunto</B>: [arch-dev-public] [RFC] systemd service files policy<BR>
<B>Fecha</B>: Thu, 23 Aug 2012 17:32:44 +0200<BR>
<BR>
<PRE>
Hi guys,
We are hard at work adding systemd service files, and I thought it
might be worth discussing a few guidelines for how to do it (should
eventually end up in the wiki I suppose, but thought it would be best
to start the discussion here).
I propose (based on input gathered on IRC) something like:
1) Use the upstream service files whenever they exist.
2) Don't do anything Arch-specific, if possible. This will maximize
our chances of not having to change behavior in the future once the
service file is provided by upstream. In particular avoid
EnvironmentFile= especially if it points to the Arch-specific
/etc/conf.d/*.
Not using an EnvironmentFile= is ok if:
2a) either the daemon has its own configuration file where the same
settings can be specified.
2b) the default service file "just works" in the most common case