similar to: [PATCH 0/2] bash-completion: Install symbolic links instead of copies of files (RHBZ#1156298).

--- bash/Makefile.am | 54 +++++++++++++++--------------------------------------- 1 file changed, 15 insertions(+), 39 deletions(-) diff --git a/bash/Makefile.am b/bash/Makefile.am index 10f0861..780da64 100644 --- a/bash/Makefile.am +++ b/bash/Makefile.am @@ -21,6 +21,10 @@ scripts = \ guestfish \ guestmount \ virt-alignment-scan \ + virt-rescue \ + virt-resize + +symlinks = \

Use CLEANFILES to remove the generated symlinks, and just ignore the errors when copying the scripts in srcdir!=builddir situations. Followup of commit 40ac54829d4e71b1bac76343872a2674a40c7ac0. --- bash/Makefile.am | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/bash/Makefile.am b/bash/Makefile.am index 780da64..ee9c10c 100644 --- a/bash/Makefile.am +++

Copy over the bash completion machinery from libguestfs, along with the simple completion script; use this script for all the tools. --- .gitignore | 2 + Makefile.am | 3 ++ bash/Makefile.am | 68 +++++++++++++++++++++++++++++++++ bash/README | 6 +++ bash/test-complete-in-script.sh | 40 +++++++++++++++++++

On Friday 31 October 2014 20:03:22 Hilko Bengen wrote: > @@ -87,10 +59,14 @@ if HAVE_BASH_COMPLETION > bashcompletiondir = $(BASH_COMPLETIONS_DIR) > #bashcompletion_DATA = $(scripts) > > -all-local: $(scripts) > +all-local: $(scripts) $(symlinks) > + test $(srcdir) != $(builddir) && cd $(srcdir) && cp $(scripts) > $(abs_builddir)/ > >

On Friday 24 October 2014 09:14:29 Richard W.M. Jones wrote: > Previously we copied the files instead of the symlinks. This series LGTM. On the other hand, given that the symlinks in the builddir are not used at all, why not just create them only at install time? -- Pino Toscano

This implements most of RHBZ#1367738. I didn't bother with virt-v2v-copy-to-local and virt-win-reg, but all the other tools now have full bash completion. Rich.

Hello, There are three small problems with the "slogin" and "slogin.1" symlinks created upon installation: 1. "./" is included in the target path unnecessarily. 2. Symlinks are assumed to be available, while only hardlinks could. 3. EXEEXT is not respected for slogin. Here is a fix for both problems -- the "./" is simply removed, EXEEXT is added, the

On Tue, Feb 25, 2014 at 05:29:08PM +0100, Pino Toscano wrote: > +let xdg_config_dirs ~prog = > + let dirs = > + try Sys.getenv "XDG_CONFIG_DIRS" > + with Not_found -> "/etc/xdg" in This seems to put the virt-builder config files into /etc/xdg/virt-builder which is kind of annoying. Can we move them to a regular default location (/etc/virt-builder)? I

Add new scripts for: - guestunmount - virt-copy-in - virt-copy-out - virt-customize - virt-dib - virt-diff - virt-get-kernel - virt-p2v-make-disk - virt-p2v-make-kickstart - virt-p2v-make-kiwi - virt-tar-in - virt-tar-out Also combine the separate virt-resize script into the general script virt-alignment-scan. There wasn't really any reason to have separate scripts. --- .gitignore

In general, autotooled packages are supposed to allow './configure --prefix=$HOME/subdir' as a way to then get 'make install' to run as non-root. In fact, 'make distcheck' tests that this scenario works; alas, we fail due to: /usr/bin/install -c -m 644 ../../../bash/nbdkit '/usr/share/bash-completion/completions' /usr/bin/install: cannot remove

When files with pre-0.9.9 tool names exists in $(exec_prefix)/bin, "make DESTDIR=${staging_dir} install" tries to delete them, which may cause a failure for lack of permissions (quite likely to happen when building a package as a normal user), and is wrong anyway (nothing outside of DESTDIR should ever be changed by "make install"). With this patch, it will now cd to

2008/7/16 John Ferlito <johnf at inodes.org>: >> Now there's the minor problem of upgrading from an earlier version of >> oggz, and having both versions of the >> tools around (eg. having an old oggzdump lying around even as >> oggz-dump is upgraded). What are your thoughts about ways to deal with >> this? eg. >> >> * On 'make install',

Still don't recommend you use 'make install', but here we go. Rich.

On Tuesday 20 May 2014 15:56:16 Richard W.M. Jones wrote: > On Tue, May 20, 2014 at 03:33:31PM +0200, Pino Toscano wrote: > > Resolve the given path within the chroot, so scrub can be invoked > > outside the chroot on an already-resolved path. > > Given that realpath is used, its availability is checked manually, > > since scrub-file already depends on the

Hi, I want to cross-compile samba for arm-linux. I have host machine: Red Had Enterprise Edition 5.0 and I am not able to cross compile it. I tried 3-4 Versions of samba but in vain. Can you guide me through compiling process.Which stable version of samba should i use?Step by step cross compilation process.OR If you have binaries or package for samba which i can?directly?use ?at my arm machine.

--- builder/Makefile.am | 3 ++- builder/opensuse.conf.in | 3 +++ builder/opensuse.gpg | 21 +++++++++++++++++++++ configure.ac | 1 + 4 files changed, 27 insertions(+), 1 deletion(-) create mode 100644 builder/opensuse.conf.in create mode 100644 builder/opensuse.gpg diff --git a/builder/Makefile.am b/builder/Makefile.am index 4bed54c..e8f8dfb 100644 ---

Hi guys, Here are two patches to get opensuse images in virt-builder. Cédric Bosdonnat (2): Allow curl to follow redirects. builder: add opensuse images sources builder/Makefile.am | 3 ++- builder/downloader.ml | 4 ++-- builder/opensuse.conf.in | 3 +++ builder/opensuse.gpg | 21 +++++++++++++++++++++ configure.ac | 1 + 5 files changed, 29 insertions(+), 3

The real sudo does it as well, and leaving them when preserving the environment (-E) maybe breaks the applications, as e.g. chroot will have a TMPDIR path pointing outside of it. --- dib/dib.ml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/dib/dib.ml b/dib/dib.ml index df83ba1..d15cd19 100644 --- a/dib/dib.ml +++ b/dib/dib.ml @@ -301,6 +301,11 @@ if [ -z \"$preserve_env\" ];

I need to generate a minimal Samba working in a SH4 cpu in a STLinux 2.3 environment. The goal is to have very very simple Samba server running in a STLinux environment. STLinux Kernel has included the CIFS support. Really I'm a newbie in Samba cross-compilation. And obviously I've problems :-( Any help will be appreciated. Thanks :-) 1) First of all I've set some env vars: export

I''m trying to make puppetlabs_spec_helper runs on Windows 7 to test my Puppet modules. Is this supported ? Because I encountered some problems: 1. symlinks were not created on Windows 7 (even if the functionnality are availabe). To manage that I added to rake_tasks.rb an ugly function: def make_link(source,target) ruby_platform =