Re: FYI: rpmbuild gets slightly stricter, files listed twice now terminates build

On Jan 24, 2012, at 11:36 AM, Matthew Dawkins wrote:

> 
> 
> So POK just curious how do I properly do this?
> 
> the following in a spec:
> %dir %{_datadir}/unity
> %{_datadir}/unity/
> 

Remove the %dir is the packaging fix here.

But more generally, there are almost certainly going to be some glitches
because its rather tricky matching up an implementation with expectations.

And the transition (and the associated "brain farts") are even
more painful because there isn't a hard/fast rule, particularly
when "legacy compatible" is the sine qua non against which
changes to RPM are usually measured.


>  gives me this error now:

The "now" here is implicitly a statement
	This used to work! You broke something! What did you change?

This is a rather silly way to develop code (but is always how RPM has been developed).

The better development process is to write explicit coverage
tests and put them into an automated test harness under
a buildbot with "continuous integration".

What is rate limiting on the better engineering path is solely writing
tests that approximate coverage of the problems that need solving.

All the other pieces needed for "continuous integration" and RPM development
are already implemented and in use.

73 de Jeff