All of
 help / color / mirror / Atom feed
From: Jeff Webb <>
Subject: Re: [Xenomai] Debian packaging bug in Xenomai v2.6.1
Date: Thu, 12 Jul 2012 10:14:48 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 07/12/2012 04:10 AM, Gilles Chanteperdrix wrote:
> On 07/12/2012 10:31 AM, Roland Stigge wrote:
>> On 07/12/2012 02:20 AM, Gilles Chanteperdrix wrote:
>>> The problem is that we use to have files in the /usr/share/xenomai
>>> directory, the debian files were written with this assumption, we now no
>>> longer install any file in /usr/share/xenomai, and we did not change the
>>> debian files, simply because nobody tested the debian package
>>> generation, or more accurately someone did but forgot to report the bug.
>>  From the Debian perspective, the debian/ directory in "upstream" Xenomai
>> is a bit confusing. At Debian, this one is ignored anyway and replaced
>> with Debian's up-to-date variant.
> We maintain our own debian directory for convenience, because we like
> the idea of a self-contained package. But obviously this only makes
> sense if this debian directory is maintained.
>> I unfortunately don't have the ressources to regularly sync/update
>> debian/* in the dev repository.

Do you have the resources to update debian/* on just before 
each release is made?  I don't think it's necessary to update it any 
more often than that.  I'm assuming that you eventually package each 
release anyway, so it would be nice to do it before a release is made 
official.  Of course, if you don't have time for that or your 
availability doesn't line up with the timeframe for a release, that is 
understandable.  I am just asking if the problem is trying to keep the 
git repository up to date all the time, or if you don't even have time 
to do it for each release.

> I understand that. You already maintain a debian directory on your side,
> you have absolutely no reason to maintain the debian directory of the
> xenomai project.
> Anyway, what I would like to know if people find useful the "feature" of
> shipping with a debian directory.

I find it useful, and have not had any trouble with it not working 
before.  That being said, I wouldn't object to getting the debian 
directory from another location, as long as the information at:

is updated with detailed instructions on exactly how to download, 
extract, and graft the appropriate debian directory into a xenomai 
source tree that was created from a release tarball or git repository.

Thank you for providing a mechanism to easily build debian packages.  I 
find it very valuable for many reasons.

  reply	other threads:[~2012-07-12 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 20:00 [Xenomai] [Announce] Xenomai v2.6.1 Gilles Chanteperdrix
2012-07-11 15:53 ` [Xenomai] Debian packaging bug in " Jeff Webb
2012-07-11 16:52   ` Gilles Chanteperdrix
2012-07-11 17:48     ` Lennart Sorensen
2012-07-12  0:20       ` Gilles Chanteperdrix
2012-07-12  8:31         ` Roland Stigge
2012-07-12  9:10           ` Gilles Chanteperdrix
2012-07-12 15:14             ` Jeff Webb [this message]
2012-07-12 15:41               ` Roland Stigge
2012-07-12 15:49                 ` Gilles Chanteperdrix
2012-07-12 16:02                   ` Roland Stigge
2012-07-13  7:54                     ` Willy Lambert
2012-07-13 11:21                   ` Leopold Palomo-Avellaneda
2012-07-13 12:23                     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.