On 05/16/2017 01:14 PM, Przemek Klosowski wrote:
This sender failed our fraud detection checks and may not be who they appear to be.
Learn about spoofing <
http://aka.ms/LearnAboutSpoofing> Feedback
<
http://aka.ms/SafetyTipsFeedback>
On 05/13/2017 02:55 AM, Emmanuel Seyman wrote:
> * Przemek Klosowski [12/05/2017 16:27] :
>> The only one I could see that is really provided by multiple packages is
>> /usr/bin/stap* : they seem to be provided by both systemtap-client and
>> systemtap-devel.
>> WHAT'S UP WITH THAT?
> While this should probably be considered a bug that needs to be fixed,
https://bugzilla.redhat.com/show_bug.cgi?id=1451463 And Frank Ch. Eigler closed it,
explaining that:
It turns out that this is a deliberate decision. As
outlined within the .spec file, the -devel subrpm is for building systemtap
modules (running pass 1..4); the -client subrpm is for being able to build
systemtap modules -remotely-. Both those tasks happen to be performed by the
same binary.
One could create a sub-subpackage that both subpackages depend on, but
it's getting to be silly. Is there no other option to handle this in RPM?