Ben Beasley <code@xxxxxxxxxxxxxxxxxx> writes:
> sestatus
This is based on upstream commit d464187c37529c [1]:
policycoreutils: sestatus belongs to bin not sbin
It is quite useful even to non-privileged users and doesn't require any
privileges to work, except for maybe -v.
Some tools hard code the old path, so a compatibility symlink is also
created.
- install -m 755 sestatus $(DESTDIR)$(SBINDIR)
+ # Some tools hard code /usr/sbin/sestatus ; add a compatibility symlink
+ # install will overwrite a symlink, so create the symlink before calling
+ # install to allow distributions with BINDIR == SBINDIR
+ ln -sf --relative $(DESTDIR)$(BINDIR)/sestatus $(DESTDIR)$(SBINDIR)
+ install -m 755 sestatus $(DESTDIR)$(BINDIR)
So it's should be ready for BINDIR == SBINDIR from upstream POV.
But it can't be built [2] without %{_sbindir}/sestatus until this change
is implemented:
error: Installed (but unpackaged) file(s) found:
/usr/sbin/sestatus
Installed (but unpackaged) file(s) found:
/usr/sbin/sestatus
[1] https://github.com/SELinuxProject/selinux/commit/d464187c37529ca75fd417174f39ce0eaf13efb5
[2] https://src.fedoraproject.org/rpms/policycoreutils/pull-request/41
Petr
>
> 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@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> 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@xxxxxxxxxxxxxxxxxxxxxxx
>> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> --
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
