Bug 3008 - hasher should manifest itself
: hasher should manifest itself
Status: CLOSED FIXED
: Sisyphus
(All bugs in Sisyphus/hasher)
: unstable
: all Linux
: P2 enhancement
Assigned To:
:
:
:
:
:
  Show dependency tree
 
Reported: 2003-09-18 20:59 by
Modified: 2005-07-13 15:45 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2003-09-18 20:59:10
Basically I think that all building environments should define something like
__BTE macro, so that one can disable some test that fail in restricted
environments and so on.
------- Comment #1 From 2003-09-22 00:44:42 -------
Could you suggest exact name for this macro, please? 
------- Comment #2 From 2003-09-22 01:04:42 -------
I'm about to add 
%__hasher 1 
to .rpmmacros file generated by hasher. 
 
------- Comment #3 From 2003-09-22 16:41:41 -------
%__BTE %(rpm -q hasher)
------- Comment #4 From 2003-09-22 17:34:26 -------
Ok, agreed, hasher will add 
%__BTE hasher 
to generated .rpmmacros file. 
 
Maybe sandman should add 
%__BTE sandman 
as well. 
------- Comment #5 From 2003-09-22 20:08:41 -------
seems some package tests should be ifdef'd explicitly with
enable/disable/with/without RPM functionality and build environment(s)
should be smart enough to pass proper --disable/--without
list to the rpmbuild phase. BTW sandman does :)
------- Comment #6 From 2003-11-25 19:46:09 -------
Since hasher is quite low level build tool , it should not decide whether to
add 
--enabled/--disable args or not.