On 01/10/2014 02:00, Richard Shaw wrote:

Hi Richard,
On Tue, Sep 30, 2014 at 5:33 PM, Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:

    On 30/09/2014 22:42, Richard Shaw wrote:

    Hi Richard,

    On Tue, Sep 30, 2014 at 4:23 PM, Bill Somerville
    <g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:

        I think 'rpm' should install dependent packages but it didn't
        work for
        me on Fedora 20 so it is still on my list to investigate further.


    What dependency are you missing? When I check I get the following
    from my RPM:
    OK, I am beginning to understand RPM packaging a bit better.

    It looks like the following one-liner will do our install from a
    bare RPM that is not in any repository including all the required
    dependencies:

    sudo yum --nogpgcheck localinstall wsjtx-1.4.0-rc2.x86_64.rpm


Pretty much. "localinstall" used to mean something but now it's just a redirect to "install" as it doesn't care if it's from a repo or a local file anymore.
OK, the place where I found it implied that it was needed for that reason but I didn't check the vintage.


    I do notice that there doesn't seem to be a one-liner reverse
    process un-install to back all the dependants that aren't used by
    anything else. That might just be my lack of RPM/yuu-Fu.

    Any comments on that Richard?


In the yum-utils package there is a helper script called "package-cleanup" which can be used to find orphans (or other issues).

$ package-cleanup --leaves

But the list needs to be reviewed line by line because not all packages that lack dependencies should be removed, such as the kernel, which is not depended upon by another package :)
Hmmm, tried that but it didn't pick up many of the packages that I thought it would. There were a bunch that I believe were orphaned when I upgraded with fedup from 18 to 20 but the Qt packages that were pulled in by the wsjtx install and all the 32-bit compatibility packages were not listed.

Sometimes yum remove seems to know what were installed as dependants other time it seems to forget and leave the leaves installed.

Richard
73
Bill
G4WJS.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to