On Sun, May 2, 2010 at 7:20 PM, Pavel Alexeev (aka Pahan-Hubbitus) wrote:
  

26.04.2010 05:04, Orcan Ogetbil пишет:
    

On Sun, Apr 25, 2010 at 7:13 PM, Kevin Kofler wrote:

      

Christoph Wickert wrote:

        

repoquery --disablerepo=\* --enablerepo=rawhide --whatrequires
ImageMagick

          

FYI, repoquery --repoid=rawhide --whatrequires ImageMagick does the trick
too.


        

That does not detect packages that require ImageMagick-c++,
ImageMagick-perl etc. The wildcard \*  seems to work. So it would be
good to run a command to include the subpackages of ImageMagick, with
the --alldeps flag, e.g.

$ repoquery --repoid=rawhide --whatrequires --alldeps ImageMagick\*
etc

Orcan

      

It produce big list of packages, thank you.

What about second part of my questions? How frequently I should (can)
update package?
    

There was a huge debate about the updating packages policy in the last
months in this list.  I don't think there is a unique answer to this
question.

I would say, it is left to the decision of the maintainer. It all
comes down how big the update is.

* Suppose there is a big API/ABI change: If you believe that you can
deal with rebuilding all the dependent packages, and support them all
in stable branches, go ahead and update. Otherwise update only in
rawhide and let people know that they need to rebuild their packages,
or rebuild them yourself.
* Just a bugfix release, with no API/ABI breakage: In this case it
should be safe to update.

I tried to answer the question as neutral as possible as I don't want
to restart the bitchfest.

Orcan