From: John Morris <john@zultron.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai Red Hat packaging
Date: Mon, 06 Jan 2014 16:40:57 -0600 [thread overview]
Message-ID: <52CB30F9.50505@zultron.com> (raw)
In-Reply-To: <52CB17A9.6080901@xenomai.org>
On 01/06/2014 02:52 PM, Gilles Chanteperdrix wrote:
> On 01/06/2014 09:10 PM, John Morris wrote:
>> Here are the packaging materials I've been using on Red Hat Enterprise
>> Linux clones for some time now, also recently updated for Fedora.
>>
>> https://github.com/zultron/xenomai-rpm
>>
>> The packaging is pretty straightforward, and follows the Debian
>> packaging for the xenomai-devel subpackage.
>>
>> A significant addition is the 'xenomai-gid-ctl' script for configuring
>> non-root access to Xenomai services, plus sysv and systemd boot init
>> scripts.
>
> Are these specific to Red Hat, or can we put them in the set of files
> installed by default?
The 'xenomai-gid-ctl' script should work anywhere.
The 'xenomai.default' file (installed into /etc/default/xenomai) works
with RH- & Debian-derivatives, and other distros with the /etc/default
directory. /etc/default/xenomai is only used to override the default
'xenomai' group, is semi-optional, and may be relocated.
Installing 'xenomai-gid-ctl' (and 'xenomai.default', if /etc/default
exists) from 'make install' could be useful to the end user, since it is
a stand-alone utility.
The EL6 sysv init script needs modification to support Debian's LSB init
system, simple for someone more familiar.
Other projects I'm familiar with often ship system init scripts in a
e.g. 'contrib' directory, and don't include complex makefile logic to
detect distro and install the correct init script. Manual installation
is left up to the end user or the packager.
> I'd appreciate comments on the control script's correctness
>> and the init scripts' utility.
>
> You do not need to pass --enable-x86-tsc as it is enabled by default
> now.
Thanks!
> As for building the doc, xenomai sources contain generated
> documentation, so if you do not enable any option, you will have some
> documentation installed. If you still want to generate the doxygen
> documentation, what is the problem with --enable-dox-doc?
I'll find time to revisit doc generation and report back.
John
next prev parent reply other threads:[~2014-01-06 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:10 [Xenomai] Xenomai Red Hat packaging John Morris
2014-01-06 20:52 ` Gilles Chanteperdrix
2014-01-06 22:40 ` John Morris [this message]
2014-04-20 16:53 ` Gilles Chanteperdrix
2014-04-21 22:21 ` John Morris
2014-04-21 22:28 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CB30F9.50505@zultron.com \
--to=john@zultron.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.