How do I tell from source rpm's: 1) the build order of gstreamer packages 2) the command line args for the ./configure For centos 7. Thanks, Jerry
In article <CABr8-B6PS8WGd_tyTCu8cG9veh1QKeuu8rR7TNbyZ+sFbo=uFA at mail.gmail.com>, Jerry Geis <jerry.geis at gmail.com> wrote:> How do I tell from source rpm's: > 1) the build order of gstreamer packages > 2) the command line args for the ./configure > > For centos 7.Look in the .spec file, specifically at the %prep, %build, and %install sections. For more than you ever wanted to know, see http://ftp.rpm.org/max-rpm/ particularly chapter 13. Cheers Tony -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org
On Mon, Oct 14, 2019 at 09:06:11PM -0400, Jerry Geis wrote:> How do I tell from source rpm's: > 1) the build order of gstreamer packagesThis isn't specifically defined in the source RPM, but rather, the RPM Spec file lists build dependencies, and you'll have to figure that out. https://git.centos.org/rpms/gstreamer/blob/c7/f/SPECS/gstreamer.spec#_22 and the gstreamer-plugins-base source package has a bunch of dependencies too: https://git.centos.org/rpms/gstreamer-plugins-base/blob/c7/f/SPECS/gstreamer-plugins-base.spec#_19> 2) the command line args for the ./configurehttps://git.centos.org/rpms/gstreamer/blob/c7/f/SPECS/gstreamer.spec#_123 Keep in mind that %configure is a macro that has many additional arguments, ones that are standardized across the build environment for CentOS. The additional arguments to %configure are gstreamer-specific. -- Jonathan Billings <billings at negate.org>
On 10/14/19 9:06 PM, Jerry Geis wrote:> How do I tell from source rpm's: > 1) the build order of gstreamer packagesI replied from my phone yesterday, and it doesn't appear to have gone through... The _chronological_ build order is most easily inferred from the RPM tag %{BUILDTIME}.? Usage example: +++++++++++ [lowen at dhcp-pool102 ~]$ rpm -qa --qf "%{BUILDTIME} -- %{NAME}\n" |grep gstreamer1|sort 1501713160 -- gstreamer1 1501713160 -- gstreamer1-devel 1502039500 -- gstreamer1-plugins-good 1523411572 -- gstreamer1-plugins-bad-free 1523411572 -- gstreamer1-plugins-bad-free-gtk 1523411627 -- gstreamer1-plugins-ugly-free 1540923990 -- gstreamer1-plugins-base 1540923990 -- gstreamer1-plugins-base-devel [lowen at dhcp-pool102 ~]$ +++++++++ It's pretty easy to see which packages were built at the same time, and the chronological order the others were built in.? To query this from a set of src.rpms just use 'rpm -qp ....' with the full package filename(s) instead of just the package name.? I used -qa and a grep feeding a sort to keep it 'simple,' although I have mixed repositories represented in that build order.? With a set of src.rpms you have better control of what you're checking in terms of the order of the build.