Bug 3008 - hasher should manifest itself
Summary: hasher should manifest itself
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: hasher (show other bugs)
Version: unstable
Hardware: all Linux
: P2 enhancement
Assignee: Dmitry V. Levin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-18 20:59 MSD by at@altlinux.org
Modified: 2005-07-13 15:45 MSD (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description at@altlinux.org 2003-09-18 20:59:10 MSD 
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 Dmitry V. Levin 2003-09-22 00:44:42 MSD 
Could you suggest exact name for this macro, please?
Comment 2 Dmitry V. Levin 2003-09-22 01:04:42 MSD 
I'm about to add 
%__hasher 1 
to .rpmmacros file generated by hasher.
Comment 3 at@altlinux.org 2003-09-22 16:41:41 MSD 
%__BTE %(rpm -q hasher)
Comment 4 Dmitry V. Levin 2003-09-22 17:34:26 MSD 
Ok, agreed, hasher will add 
%__BTE hasher 
to generated .rpmmacros file. 
 
Maybe sandman should add 
%__BTE sandman 
as well.
Comment 5 Sergey Bolshakov 2003-09-22 20:08:41 MSD 
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 Dmitry V. Levin 2003-11-25 19:46:09 MSK 
Since hasher is quite low level build tool , it should not decide whether to add 
--enabled/--disable args or not.