I've always had mixed feelings about tracking paths from
build into M4/RPM macros.
The uglix paradigm is to use PATH searches, not absolute paths.
When I first implemented, there were still significant differences
between, say "mkdir -p", or lack of install(1), which were
quite tedious to deal with.
Another reason for enumerating absolute paths was to
permit, say, cross-compiles to overload tool-chain
paths without the necessity of envar's (which are
painful to support in *.spec files in RPM because
not everything is a shell environment, which would force
RPM to dynamically manage the the envar's as a build
proceeds, with the usual limitation that children cannot
change a parent's envcar's (but could change a parent's
macros in a single build).
But I'm not sure there's any reason to attempt to provide
a name space of absolute paths to executables any more.
*shrug*
Hurts little, just the digests on tests/ref/showrc get excited
not only with new additions like adding @__RUBY@/%{__ruby}, but
also if one hasn't installed some executable, and so the default,
not the specific, absolute path is shoved into macros.
73 de Jeff
On Oct 15, 2010, at 11:51 PM, Per Øyvind Karlsen wrote:
> RPM Package Manager, CVS Repository
> http://rpm5.org/cvs/
> ____________________________________________________________________________
>
> Server: rpm5.org Name: Per Øyvind Karlsen
> Root: /v/rpm/cvs Email: pkarl...@rpm5.org
> Module: rpm Date: 16-Oct-2010 05:51:05
> Branch: HEAD Handle: 2010101603510500
>
> Modified files:
> rpm configure.ac
>
> Log:
> add ruby macros from mandriva.
>
> Summary:
> Revision Changes Path
> 2.463 +1 -0 rpm/configure.ac
> ____________________________________________________________________________
>
> patch -p0 <<'@@ .'
> Index: rpm/configure.ac
> ============================================================================
> $ cvs diff -u -r2.462 -r2.463 configure.ac
> --- rpm/configure.ac 16 Oct 2010 03:48:51 -0000 2.462
> +++ rpm/configure.ac 16 Oct 2010 03:51:05 -0000 2.463
> @@ -503,6 +503,7 @@
> AC_PATH_PROG(__PYTHON, python, %{_bindir}/python, $MYPATH)
> AC_PATH_PROG(__RM, rm, /bin/rm, $MYPATH)
> AC_PATH_PROG(__RSH, rsh, %{_bindir}/rsh, $MYPATH)
> +AC_PATH_PROG(__RUBY, ruby, %{_bindir}/ruby, $MYPATH)
> AC_PATH_PROG(__SED, sed, /bin/sed, $MYPATH)
> AC_PATH_PROG(__SH, sh, /bin/sh, $MYPATH)
> AC_PATH_PROG(__SQLITE3, sqlite3, %{_bindir}/sqlite3, $MYPATH)
> @@ .
> ______________________________________________________________________
> RPM Package Manager http://rpm5.org
> CVS Sources Repository rpm-...@rpm5.org
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
