On 24 October 2014 15:33, Olav Vitters <olav@vitters.nl> wrote:
> On Fri, Oct 24, 2014 at 01:48:33PM +0300, Aigars Mahinovs wrote:
>> No, but we set up requirements that their work must meet before it can
>> enter archive or may end up in a release. That is what the whole of
>> Debian Policy is about.
>
> That is things within the package itself. This is about doing extra
> work. In case you rely on functionality which is only provided by one
> init system, ensure the functionality is also available on other init
> systems.
That is not what is actually required. It is sufficient to handle the
situation when such functionality is not available. That is inside the
package and it has many different uses (different init, no init,
restricted chroot, system in some weird state, API changed, ...). You
can even hide that code behind a command-line option or a
wrapper-script (so you don't have to detect availability of feature
and instead rely on being called with a special option or name when
extra functionality does not exist). No one is forcing you to
implement features into another init system, so that is a strawman.
--
Best regards,
Aigars Mahinovs mailto:aigarius@debian.org
#--------------------------------------------------------------#
| .''`. Debian GNU/Linux (http://www.debian.org) |
| : :' : Latvian Open Source Assoc. (http://www.laka.lv) |
| `. `' Linux Administration and Free Software Consulting |
| `- (http://www.aiteki.com) |
#--------------------------------------------------------------#
--
To UNSUBSCRIBE, email to debian-vote-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: https://lists.debian.org/CABpYwDWTeyfD2PixwTSOy5VW4sXhkq=36rMPfXHJaiZD7mQi-A@mail.gmail.com