All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <haberlerm@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Q on xenomai2/3 userland coexistence
Date: Sat, 27 Jun 2015 14:43:39 +0200	[thread overview]
Message-ID: <20150627124339.GD9756@hermes.click-hack.org> (raw)
In-Reply-To: <C31C0BF8-AC9A-442B-8A2F-4576ACF1F817@gmail.com>

On Sat, Jun 27, 2015 at 02:22:09PM +0200, Michael Haberler wrote:
> ATM we're sorting through the machinekit xenomai3 transition on
> debian
> 
> I assume that users will continue to run xenomai2 kernels for a
> long time, so we work towards separate (but hopefully
> coexisting-in-peace) packages for Xenomai2 and Xenomai3 (startup
> is driven by kernel autodetection, so booting a different kernel
> chooses the right runtime)
> 
> The libxenomai-dev and libxenomai1 in debian are all xenomai2 atm,
> but I assume Xenomai3 equivalents will appear eventually

Xenomai 3 has a debian directory allowing to build it as a Debian
package. So, in fact, they are already here.


> 
> I hope these will be able to co-reside on the same host?
> 
> Ideally suggesting the Xenomai3 packages would be separate, be named differently, and not supersede any installed Xenomai2 packages?
> 
> 
> (or am I blundering and I can run applications linked against the Xenomai3 libraries on a Xenomai2 kernel? my tests so far indicate - not)
> 

I was afraid someone was going to ask for that. Experience has
proved that allowing to install silently several versions of Xenomai
is a recipe for trouble. So, relying on Debian allowing to install
only one version of the package was a nice feature.

So, if we agree that having the two versions installed is not
something for the common user, I would suggest people who want to do
that know what they are doing and can install one version as a
Debian package, and the other manually.

On the other hand, if we think having the two versions installed
will be a very common use case, I do not think there is any conflict
with library names, only with tool names, and since we provide the
the "xeno" wrapper to fetch the tools from another place than
/usr/bin, I guess the only conflict would be on the "xeno" wrapper
itself. So, maybe we could call it xeno3 in Xenomai3 Debian package
to avoid any issue? Or use the Debian "alternatives" mechanism
(though this mechanism is probably unknown from the typical ubuntu
user)? 

-- 
					    Gilles.
https://click-hack.org


  reply	other threads:[~2015-06-27 12:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27 12:22 [Xenomai] Q on xenomai2/3 userland coexistence Michael Haberler
2015-06-27 12:43 ` Gilles Chanteperdrix [this message]
2015-06-27 12:49   ` Gilles Chanteperdrix
2015-06-27 13:09 ` Philippe Gerum
2015-06-27 13:14   ` Gilles Chanteperdrix
2015-06-27 13:25     ` Michael Haberler
2015-06-27 13:37       ` Gilles Chanteperdrix
2015-06-28  6:02         ` John Morris

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=20150627124339.GD9756@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=haberlerm@gmail.com \
    --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.