Yaakov Selkowitz wrote:
> This is the hazard of using %{_libdir}/*.so.* in %files. Is there any
> reason why such a syntax should NOT be formally discouraged in the
> packaging guidelines?
There is: I do not want to have to pointlessly edit my specfile each time
some soname changes, and waste a failed build (i.e., ultimately MY time).
The other packages will need to be rebuilt ANYWAY. They may as well do so
when the Rawhide broken dependencies report comes in. Rawhide is supposed to
be a place for development, not something that always works for end users.
By the way, all this talk about keeping Rawhide usable is all the more
ridiculous given that we allow broken trunk snapshots of GCC into Rawhide
which fail to compile packages due to known regressions such as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69241 (which is keeping me from
building QtWebEngine and testing the improvements I am working on). THOSE
are the changes that hinder development and thus Rawhide's actual purpose,
not a broken dependency in one day's Rawhide compose.
Kevin Kofler
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
