SCIENTIFIC-LINUX-USERS Archives

November 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Sommerseth <[log in to unmask]>
Reply To:
Date:
Fri, 4 Nov 2016 12:01:56 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On 04/11/16 11:15, Todd Chester wrote:
> 
> 
> On 11/01/2016 11:05 PM, ToddAndMargo wrote:
>> 3) install the dependencies
>>
>> $ su -c "yum install  qt5-qtbase-devel kf5-kio-devel  kf5-karchive-devel kf5-kbookmarks-devel kf5-kcodecs-devel kf5-kcompletion-devel kf5-kcoreaddons-devel kf5-kconfig-devel  kf5-kdoctools-devel kf5-ki18n-devel  kf5-kiconthemes-devel  kf5-kitemviews-devel  kf5-knotifications-devel   kf5-kparts-devel  kf5-solid-devel   kf5-ktextwidgets-devel   kf5-kwallet-devel   kf5-kwidgetsaddons-devel  kf5-kwindowsystem-devel   kf5-kxmlgui-devel  kf5-kguiaddons-devel   extra-cmake-modules"
> 
> I was told this is an easier way, but I have not verified it:
> 
> su -c "yum-builddep krusader-2.5.0-1.fc26.src.rpm"

This will only install all the needed build dependencies a certain RPM
package depends on.  This is indeed simpler than figuring out all the
build dependencies and installing them manually.

With that said .... using mock will do that for you on-the-fly, so the
build chroot will contain only the specified dependencies as requested
by the RPM .spec file.


-- 
kind regards,

David Sommerseth

ATOM RSS1 RSS2