On Thu, Mar 28, 2013 at 11:22:46AM +0000, Sami Kerola wrote: > On Wed, Mar 27, 2013 at 10:07 PM, Sami Kerola <[email protected]> wrote: > > Signed-off-by: Sami Kerola <[email protected]> > > --- > > 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 [email protected], maybe they already have any idea how to resolve the conflicts between packages. Karel -- Karel Zak <[email protected]> http://karelzak.blogspot.com _______________________________________________ Bash-completion-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
