All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Packaging Xenomai-3
Date: Mon, 26 Jan 2015 23:17:03 +0100	[thread overview]
Message-ID: <2312262.WiWDxI5CGn@indiana> (raw)
In-Reply-To: <20150126182046.GL12812@hermes.click-hack.org>

El Dilluns, 26 de gener de 2015, a les 19:20:46, Gilles Chanteperdrix va 
escriure:
> > 
> > That's the point Gilles. Debian doesn't accept that [1].
> 
> No, you missed the point. Entirely. The point is distribution rules
> apply to re-packaging made for distributions. Not to upstream
> packages. So, basically, Xenomai upstream package does not care
> about any distribution rules, and the job of the Debian maintainer
> is to massage Xenomai installation so that it fits Debian rules.

The main idea is to collaborate with upstream in the way that both could make 
a good work that benefits all together. Obviously, this kind of rules doesn't 
affect upstream. My sentence was about that if you implement something that 
debian (or whatever distro) doesn't accept, the maintainer has double work 
patching it to be included. That's all, my propose was to have something that 
could benefit all the parts.

> Look for instance at how the libcurl3 packages are made. libcurl3 can
> use openssl, gnutls or nss as providing TLS, but was not meant to
> run the three at a time. Debian wants to be able to install the
> three version, so what does the Debian rules does ? They manage to do
> it.

AFAIK, looking the sources of the package, the names of the libraries are 
different. And installing in my box I have:

/usr/lib/x86_64-linux-gnu/libcurl-nss.so.4.3.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4.3.0
/usr/lib/x86_64-linux-gnu/libcurl.so.4.3.0

that comes from libcurl3-nss, libcurl3-gnutls and libcurl3. The last one  
(OpenSSL flavour)

> Putting things into several directories was just one proposed
> solution, but it is not by any mean the only one.

I agree. I would like to find something that could benefit all the parts. If you 
prefer not rename, no problem. I though that it could be a good idea for all. 
Also I have to say that I don't think that it has sense to implement it in 
packaging. This kind of modifications have to have a very good reason to 
diverge from upstream.

Leopold

[1] http://anonscm.debian.org/cgit/collab-maint/curl.git

-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150126/12637a25/attachment.sig>

  reply	other threads:[~2015-01-26 22:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 12:09 [Xenomai] Packaging Xenomai-3 Leopold Palomo-Avellaneda
2015-01-23 15:52 ` Gilles Chanteperdrix
2015-01-23 16:50   ` Leopold Palomo-Avellaneda
2015-01-23 17:27     ` Gilles Chanteperdrix
2015-01-24 17:56       ` Leopold Palomo-Avellaneda
2015-01-25  9:14         ` Philippe Gerum
2015-01-25 11:14           ` Leopold Palomo-Avellaneda
2015-01-25 18:10             ` Philippe Gerum
2015-01-25 18:43               ` Leopold Palomo-Avellaneda
2015-01-26 12:08                 ` Gilles Chanteperdrix
2015-01-26 12:39                   ` Leopold Palomo-Avellaneda
2015-01-26 13:38                     ` Daniele Nicolodi
2015-01-26 14:17                       ` Leopold Palomo-Avellaneda
2015-01-26 14:24                         ` Daniele Nicolodi
2015-01-26 14:01                     ` Philippe Gerum
2015-01-26 14:47                       ` Leopold Palomo-Avellaneda
2015-01-26 14:55                         ` Gilles Chanteperdrix
2015-01-26 14:08                     ` Gilles Chanteperdrix
2015-01-26 14:56                       ` Leopold Palomo-Avellaneda
2015-01-26 14:59                         ` Gilles Chanteperdrix
2015-01-26 17:46                           ` Leopold Palomo-Avellaneda
2015-01-26 18:20                             ` Gilles Chanteperdrix
2015-01-26 22:17                               ` Leopold Palomo-Avellaneda [this message]
2015-01-26 22:26                                 ` Daniele Nicolodi
2015-01-26 22:57                                   ` Leopold Palomo-Avellaneda
2015-01-26 18:32                             ` Gilles Chanteperdrix
2015-01-26 22:19                               ` Leopold Palomo-Avellaneda
2015-01-23 16:04 ` Philippe Gerum
2015-01-23 17:02   ` Leopold Palomo-Avellaneda
2015-01-23 17:24     ` Philippe Gerum
2015-01-23 17:47       ` Gilles Chanteperdrix
2015-01-24 10:05         ` Philippe Gerum
2015-01-24 17:43       ` Leopold Palomo-Avellaneda

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=2312262.WiWDxI5CGn@indiana \
    --to=leo@alaxarxa.net \
    --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.