On Aug 14, 2007, at 3:39 AM, Robert Scheck wrote:
On Tue, 14 Aug 2007, Jeff Johnson wrote:
First of all, there is no way to set the OS vendor in a path that
contains
%{_target_vendor}, eggs come from chickens.
Second, there is no defined and portable way to identify OS vendor
from
within a program, chickens come from eggs.
*args* I thought --target bing-bang-boom-bsd defines %{_target_cpu},
%{_target_vendor}, %{_target_os}, %{?_gnu}. But when we're playing
chicken
and egg and vice versa here, I now see my mistake and why it can't
work.
Good.
Off to reduce the compiled in macro set as much as possible ...
Because of my dumb question or while it's necessary? ;)
I'm trying to get the minimal necessary macro config compiled into rpm.
Way back when, there were two macro values that were used as the
basis for all paths that were "obvious" at the time:
%_usr /usr
%_var /var
and all other paths were rooted to those paths.
There's considerably more "flexibility" that has been introduced, and
I'd
like not to have to carry around independently configured, say,
%_usr
%_usrsrc
%_usrsrcrpm
%_pkgsrcdir
%_topdir
...
etc etc etc etc.
All the colon separated macro paths have %{_target}, so macro eval is
necessary,
but have expanded paths with redundant components and so will not
inheirit
from %{_usr} and %{_var} changes. The consequence is much redundancy
when reconfiguring.
All of the values need to be inheirited for argv[0] rule based
discovery of configuration,
and needs to be simplified to be relative to
%_rpmhome
lest rpmrc insanity get reinvented all over again.
But since there's no agreement on whether %_rpmhome should be
/usr/lib/[EMAIL PROTECTED]@
or
/usr/lib/rpm/@VERSION@
I'll avoid the mess for now.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
