Kristofer.Wempa at sig.com
Fri May 4 18:51:36 UTC 2012
> Yeah, don't do that. With some specs it would be extremely dangerous, especially if you build packages as root (don't do *that*, either).
> I'm all for having software that works the way we want it to work, but in this case RPM really is encouraging good habits from packagers.
> In other words, don't fight it.
> What you want to do is update your %install section, so that rather than install your files into the real, final destination, you instead install those files into the buildroot, for packaging.
Is there ANY way to get the newer RPM system to NOT use a build root ? This sort of change has a huge impact and there should be some way to get it to behave the old way .... at least for a few versions so users have a chance to make the appropriate changes. We have a very complicated build system based on RPM and this change breaks the entire system.
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
More information about the Rpm-list