On Mon, Apr 25, 2011 at 03:41:23PM +0200, Cristian Morales Vega wrote:
What's the plan for RPM in openSUSE 12.1? RPM 4.9.0 was released nearly two month ago and Factory still uses 4.8, I would rather prefer to start adapting the spec files now than later. I suppose Vincent continues modifying spec files with his new macros, it would be ugly to say him all the work needs to be undone at the last moment.
12.1 will have rpm-4.9.x.
The first step would be informing packagers of any new rules. Looking at the release notes I see two important points:
* "Dependency generators are now pluggable. Arbitrary number of dependency types is supported, new types can be added through a drop-in directory and file classification is now done with a combination of path and libmagic-type include/exclude regular expressions (XXX add link to documentation once it exists)"
How they exactly work? Something should be changed about %wx_requires?
AFAIK this only works for the internal generator, which we don't use for a couple of reasons. I'll try to port it to the external generator.
* "EXPERIMENTAL support for package "collections" which are sort of like named triggers that only run once within a transaction. This can be used for example to avoid redundant calls for cache updates etc. (XXX add link to documentation once it exists)"
Experimental? Should we use this instead of multiple calls to gtk-update-icon-cache? It's expected that openSUSE 12.1 will use a newer RPM where collections are no longer experimental?
The collection mechanism was added for the selinux folks. I don't think you should use it at the moment. (It also only helps you if you use one big transaction to install all rpms. I think you should rather fix gtk-update-icon-cache to support incremental updates.)
And this would be nice:
* "Short-circuiting binary builds is now allowed by rpmbuild for developer convenience while testing. Short-circuited packages are tainted with an unsatisfiable dependency to limit their use for the intended testing-only purpose."
How? Is this possible through "osc build"?
It's just a option that needs to be passed to rpmbuild, so maybe osc build doesn't need to be changed. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org