From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Romain Lenglet <rlenglet@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Packaging issues - part 3
Date: Mon, 17 Oct 2005 20:48:29 +0200 [thread overview]
Message-ID: <17235.61949.261241.654277@domain.hid> (raw)
In-Reply-To: <200510162325.03410.rlenglet@domain.hid>
Romain Lenglet wrote:
> > This looks like separated issues: fixes of the debian
> > directory may go in the Xenomai svn repository, and cause a
> > debian package update without a new upstream release. But
> > there are maybe other issues ?
>
> Alright, but we should be able to make changes in both the
> Xenomai code and the Debian files, independently.
> If a package has been released, then if we want to release a new
> revision of the package that corrects Debian-only issues, then
> we must be able to ignore any modification in the repository
> that do not concern the Debian files, to create the new package.
>
> We can do that with either separate repositories, or branches in
> svn.
Handling a separate branch mean seems a lot of maintenance, whereas
updates of the debian packaging system would go in the debian directory
(I mean, except manapges ;-), and work on the trunk would never change
the debian directory.
Maybe a lighter solution would be to maintain the debian directory at
another place in the repository, for example in packages/debian, and to
make it appear in trunk using the subversion svn:external attribute.
This way the debian directory would appear in all the releases of
xenomai.
--
Gilles Chanteperdrix.
prev parent reply other threads:[~2005-10-17 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 7:58 [Xenomai-core] Packaging issues - part 3 Romain Lenglet
2005-10-16 8:12 ` Gilles Chanteperdrix
2005-10-16 14:25 ` Romain Lenglet
2005-10-17 18:48 ` Gilles Chanteperdrix [this message]
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=17235.61949.261241.654277@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rlenglet@domain.hid \
--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.