On Sep 14, 2012, at 6:55 PM, Elan Ruusamäe <[email protected]> wrote:
> On 14/09/12 21:16, Jeffrey Johnson wrote: >> Sh*t happens. > yeah, rpm 4.5 (and 4.4.9 and 4.4.2) took the dump if i first 256 bytes > contained 0x7f..0xff byte > > here's test spec for it: > http://git.pld-linux.org/?p=packages/test.git;a=blob;f=test.spec;h=4d2bb35f8683e15bd3fc7069d5431cc649738678;hb=7451100f7d57d6866078b5a8a24962cec7e505a2 > Here are the 1st 3 lines of test.spec: 1 # "Õ" - an unicode character in first 256 byte of a spec makes spec invalid 2 %include /usr/lib/rpm/macros.java 3 Summary: test package to run COMMAND like commands on builder :/ line #2 can be written %{load:%{_usrlibrpm}/macros.java} The benefit of using %{load:…} rather than %include is that the syntax of macro config files, not *.spec, is used while parsing. Specifically that means no need for %define, and multiline macros with escaping are better supported. RPM will be refactoring most build macros out of "default" configuration expecting *.spec files (or build systems) to determine what macros need to be loaded. The reason is that there are now ~500 macros being carried around through all modes of operation, of which maybe 50 have any use outside of package building. hth 73 de Jeff _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
