From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux@vger.kernel.org, kerolasa@iki.fi,
bash-completion-devel@lists.alioth.debian.org
Subject: Re: [PATCH 01/10] bash-completion: add bash completetion configure option
Date: Fri, 29 Mar 2013 10:42:18 +0100 [thread overview]
Message-ID: <20130329094218.GG24678@x2.net.home> (raw)
In-Reply-To: <CAG27Bk08gHsgy-mdJu_a_QE6oimShXxYVJFaSpZ_O9Xybbe8+w@mail.gmail.com>
On Thu, Mar 28, 2013 at 11:22:46AM +0000, Sami Kerola wrote:
> On Wed, Mar 27, 2013 at 10:07 PM, Sami Kerola <kerolasa@iki.fi> wrote:
> > Signed-off-by: Sami Kerola <kerolasa@iki.fi>
> > ---
> > Makefile.am | 5 +++++
> > configure.ac | 13 +++++++++++++
> > shell-completion/Makemodule.am | 1 +
> > 3 files changed, 19 insertions(+)
> > create mode 100644 shell-completion/Makemodule.am
>
> Do we need './configure
> --disable-overwriting-bash-compilation-package-files'?
Hmm... not sure, it's distro specific decision/policy.
Maybe we need --disable-bash-completion, it should enough.
> I realized some of the files I wrote will conflicting with the
Which files? We can add some info to ReleaseNotes to make it easy for
distros.
> http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=tree;f=completions
What about to use .ul (or .util-linux) suffix for the conflicting
files and in the bash-completion package check for these files and use
it if exists? See for example:
http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=blob;f=completions/umount
CC: to bash-completion-devel@lists.alioth.debian.org, maybe they
already have any idea how to resolve the conflicts between packages.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-03-29 9:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 22:07 [PATCH 00/10] [pull] bash-completion Sami Kerola
2013-03-27 22:07 ` [PATCH 01/10] bash-completion: add bash completetion configure option Sami Kerola
2013-03-28 11:22 ` Sami Kerola
2013-03-29 9:42 ` Karel Zak [this message]
2013-03-27 22:07 ` [PATCH 02/10] bash-completion: disk-utils Sami Kerola
2013-03-28 1:42 ` Dave Reisner
2013-04-01 15:54 ` Sami Kerola
2013-03-28 9:54 ` Karel Zak
2013-04-01 17:00 ` Sami Kerola
2013-03-27 22:07 ` [PATCH 03/10] bash-completion: fdisks Sami Kerola
2013-03-28 10:01 ` Karel Zak
2013-03-27 22:07 ` [PATCH 04/10] bash-completion: login-utils Sami Kerola
2013-03-28 1:42 ` Dave Reisner
2013-04-01 16:05 ` Sami Kerola
2013-03-28 10:05 ` Karel Zak
2013-04-01 16:06 ` Sami Kerola
2013-03-27 22:07 ` [PATCH 05/10] bash-completion: misc-utils Sami Kerola
2013-03-28 1:42 ` Dave Reisner
2013-04-01 16:52 ` Sami Kerola
2013-03-27 22:07 ` [PATCH 06/10] bash-completion: schedutils Sami Kerola
2013-03-27 22:07 ` [PATCH 07/10] bash-completion: sys-utils Sami Kerola
2013-03-29 16:33 ` Karel Zak
2013-04-01 16:32 ` Sami Kerola
2013-04-05 14:44 ` Karel Zak
2013-03-27 22:07 ` [PATCH 08/10] bash-completion: term-utils Sami Kerola
2013-03-28 10:06 ` Karel Zak
2013-03-27 22:07 ` [PATCH 09/10] bash-completion: text-utils Sami Kerola
2013-03-27 22:07 ` [PATCH 10/10] bash-completion: add completion files to Makefile.am Sami Kerola
2013-03-28 1:42 ` [PATCH 00/10] [pull] bash-completion Dave Reisner
2013-03-28 9:37 ` Karel Zak
2013-03-31 23:49 ` Sami Kerola
2013-04-01 15:44 ` Sami Kerola
2013-04-05 14:11 ` Karel Zak
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=20130329094218.GG24678@x2.net.home \
--to=kzak@redhat.com \
--cc=bash-completion-devel@lists.alioth.debian.org \
--cc=kerolasa@gmail.com \
--cc=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox