Possible Improvement of "Installing software from source on Fedora" #553

Closed
opened 2023-02-01 12:59:39 +00:00 by pboy · 3 comments

The following suggestions / questions are from a thread on discussion

"Usually, I will only take this route when neccessary. It is usually certain feature from a application only exist in some version, which the RPM is older.

What I need from the document is:

  1. How about avoid both RPM and source conflict with each other

    • I usually use RPM to install the older version then install by source, as it usually will take care of dependency issues for the source version
  2. What will be the implication for future updates like “dnf upgrade”

  3. Common issues that might arise when doing install by source version

    • selinux policy
    • firewall
    • that is, all the steps taken care by dnf, now needs to be done manually.

see:
https://discussion.fedoraproject.org/t/46229/5

The following suggestions / questions are from a thread on discussion "Usually, I will only take this route when neccessary. It is usually certain feature from a application only exist in some version, which the RPM is older. What I need from the document is: 1. How about avoid both RPM and source conflict with each other * I usually use RPM to install the older version then install by source, as it usually will take care of dependency issues for the source version 2. What will be the implication for future updates like “dnf upgrade” 3. Common issues that might arise when doing install by source version * selinux policy * firewall * that is, all the steps taken care by dnf, now needs to be done manually. see: https://discussion.fedoraproject.org/t/46229/5
Contributor

There is a PR made already by Alan. @pboy you can close this.

https://pagure.io/fedora-docs/quick-docs/issue/111

There is a PR made already by Alan. @pboy you can close this. https://pagure.io/fedora-docs/quick-docs/issue/111
Contributor
Closing this now due to PR merged #548 by @pboy https://pagure.io/fedora-docs/quick-docs/pull-request/548
Contributor

Metadata Update from @hankuoffroad:

  • Issue close_status updated to: complete
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @hankuoffroad**: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Docs/quick-docs#553
No description provided.