FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

LinkBack Thread Tools
Old 02-14-2011, 09:17 AM
Marco Amadori
Default Upstart and sysvinit in packages - Policy needed

In data Saturday 12 February 2011 05:55:16, Joachim Breitner ha scritto:

>> I included some patches to have nodm gracefully uses the upstart job.

>> Since those patches permits to have both init scripts in the system, no
>> matter if upstart or sysvinit is used, a little more effort is required
>> to proper build this package.

> thanks for your patches. I applied them to the repo besides the patch
> 0005-Exit-from-the-sysvinit-script-to-use-the-upstart-job.patch. Is that
> code taken from some existing package?

I took the idea from discussion on bug #591791 and updated to work also with
current sysvinit, that does currently not likes the syntax "--version".

I include again this patch to permits other people to follow the discussion
there, but is just a matter of :

if [ -e "/etc/init/${NAME}.conf" ] && /sbin/telinit --version >/dev/null 2>&1
| grep -qs upstart
exit 0

inside the sysvinit init script.

> I feel like the semantics of both
> upstart jobs and init scripts in one package should be the same across
> packages, so I’d rather see a common solution for that.

Yes, probably something better and simpler than my lines above should emerge
from the discussion.

>> But I'm stuck as you are (in the git repo) because dh will refuse to add
>> an init.d script if an upstart job is available.
>> Any hints on how to neatly have both init script files on the binary
>> package?

> Maybe you could raise the issue on d-devel?

I CCed the bug in the policy that seems to be the best match for the
discussion, anyway I'll CC also d-devel to have some help.

Even if all agrees that my code above is right (a thing that I cannot imagine
to be true in any universe), if it vital that a policy is given for that

I think it would be interesting for wheezy to easely permit an Admin to choose
an alternate init system and to permit to package maintainer to carefully
provide init script tailored for a particular system of interest.

Debhelper seems to not permit to have both, e.g., an upstart and a sysvinit
script available in the package, although with a trick like the above
mentioned one, the could happily live together in perfect armony, side by side
on my wheezy.


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Thread Tools

All times are GMT. The time now is 05:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org