[arch-dev-public] [RFC] systemd service files policy

Rashif Ray Rahman schiv at archlinux.org
Thu Aug 30 11:52:36 EDT 2012

On 30 August 2012 23:40, Tom Gundersen <teg at jklm.no> wrote:
> On Thu, Aug 30, 2012 at 5:07 PM, Sébastien Luttringer <seblu at seblu.net> wrote:
>> On Thu, Aug 23, 2012 at 5:32 PM, Tom Gundersen <teg at jklm.no> wrote:
>>> 1) Use the upstream service files whenever they exist.
>> This should be a SHOULD and not a MUST. Some service files can be
>> poorly implemented or some deps are missing (e.g. your point 5) and be
>> overloaded by maintainer.
> Makes sense. Like with any other part of the packages, we might need
> to patch things until they are fixed upstream.

What concerns me is the "overloaded by maintainer" part. For e.g.,
what if the maintainer disagrees with one single approach that appears
to come from our distribution? Do we then have to keep our own service
file "fork"?


More information about the arch-dev-public mailing list