From: "Christoph Egger" <Christoph.Egger@amd.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] yet another package check
Date: Thu, 14 Dec 2006 15:22:15 +0100 [thread overview]
Message-ID: <200612141522.15699.Christoph.Egger@amd.com> (raw)
In-Reply-To: <4581688F.76E4.0078.0@novell.com>
Why do you write non-portable shell scripts?
Some time ago, I made these portable:
check_brctl
check_iproute
check_libvncserver
check_python
check_sdl
check_zlib_devel
check_zlib_lib
For now, the non-portable scripts are:
check_crypto_lib
check_openssl_devel
check_python_devel
check_udev
check_x11_devel
Can you make them portable (again), please?
On Thursday 14 December 2006 15:06, you wrote:
> As before, the file added to tools/check/ must be given exec permission.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> Index: 2006-12-11/tools/Makefile
> ===================================================================
> --- 2006-12-11.orig/tools/Makefile 2006-12-04 08:49:57.000000000 +0100
> +++ 2006-12-11/tools/Makefile 2006-12-14 14:25:02.000000000 +0100
> @@ -36,7 +36,7 @@ all: check
> $(MAKE) ioemu
>
> .PHONY: install
> -install: check
> +install: check_install
> @set -e; for subdir in $(SUBDIRS-y); do \
> $(MAKE) -C $$subdir $@; \
> done
> @@ -58,6 +58,10 @@ distclean: clean
> check:
> $(MAKE) -C check
>
> +.PHONY: check_install
> +check_install: check
> + $(MAKE) -C check install
> +
> .PHONY: check_clean
> check_clean:
> $(MAKE) -C check clean
> Index: 2006-12-11/tools/check/check_python_xml
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ 2006-12-11/tools/check/check_python_xml 2006-12-14 14:05:30.000000000
> +0100 @@ -0,0 +1,16 @@
> +#!/bin/bash
> +# CHECK-INSTALL
> +
> +function error {
> + echo
> + echo " *** Check for python-xml package FAILED"
> + exit 1
> +}
> +
> +python -c '
> +import os.path, sys
> +for p in sys.path:
> + if os.path.exists(p + "/xml/dom/minidom.py"):
> + sys.exit(0)
> +sys.exit(1)
> +' || error
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-12-14 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 14:06 [PATCH] yet another package check Jan Beulich
2006-12-14 14:22 ` Christoph Egger [this message]
2006-12-14 14:27 ` Guillaume Rousse
2006-12-14 14:32 ` Christoph Egger
2006-12-14 15:23 ` Jan Beulich
2006-12-14 17:38 ` Brendan Cully
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=200612141522.15699.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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.