[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: F40 Change Proposal: F40 Change Proposal: Unify /usr/bin and /usr/sbin (System-Wide)
From:       Ben Beasley <code () musicinmybrain ! net>
Date:       2024-01-17 17:45:03
Message-ID: cac2c649-0474-4adf-9300-271872000018 () musicinmybrain ! net
[Download RAW message or body]

I attempted a quick check:

     $ repoquery -q --repo=rawhide -l -a | tee >(

         grep -E '^/usr/bin/[^/]+$' | sort -u | xargs -n 1 basename > 
bin.txt

         ) | grep -E '^/usr/sbin/[^/]+$' | sort -u | xargs -n 1 basename 
 > sbin.txt

     $ wc -l bin.txt sbin.txt

      31229 bin.txt
       2998 sbin.txt
      34227 total

     $ comm -1 -2 bin.txt sbin.txt

     arping
     backintime-qt-root
     bat
     beesu
     chkrootkit
     etherape
     exabgp-healthcheck
     faxq
     gearmand
     hcidump
     hddtemp
     hunt
     ifstat
     iscsistart
     lshw-gui
     lspci
     makemap
     mate-system-log
     msktutil
     named-checkconf
     named-checkzone
     named-compilezone
     pidof
     ping
     ptdump
     rdistd
     rhino
     rpcbind
     rpcinfo
     sendfax
     sestatus
     setup
     sievec
     subscription-manager
     system-switch-java
     tmpwatch
     tracepath
     udevadm
     updatedb
     v4l-conf
     vpnc
     vpnc-disconnect

That should be a reasonably accurate list of the executables that need 
investigation, and for which the packages that provide them probably 
need some kind of modification.

On 1/7/24 10:47, Gary Buhrmaster wrote:
> On Wed, Dec 20, 2023 at 7:54 PM Aoife Moloney <amoloney@redhat.com> wrote:
>> Wiki -> https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin
>>
> I do not see as part of the plan a process to
> go through all Fedora packages and identifying
> binaries in /usr/bin that have the same name
> as a binary in /usr/sbin (from the same, or
> different packages) such that the packager
> (or the multiple packages) will need to
> coordinate the changes (perhaps by engaging
> upstream).
>
> I agree that there should be few, but
> identifying impacts in advance provides
> for a better decision process, and minimizes
> the last minute work that packagers need
> to do (they will have a longer warning and
> preparation time).
> --
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[prev in list] [next in list] [prev in thread] [next in thread]