| |
@@ -18,12 +18,12 @@
|
| |
* Libraries must be installed to `/usr/lib[64]`.
|
| |
* Headers must be installed to `/usr/include`.
|
| |
* Executables must be installed to a location in the default system
|
| |
- `$PATH`
|
| |
+ `$PATH`
|
| |
* Other -devel functionality such as pkgconfig files must be installed
|
| |
- in their standard lookup locations.
|
| |
+ in their standard lookup locations.
|
| |
* Installed services may own a well-known DBUS address.
|
| |
* Services may own the appropriate standard TCP/UDP ports or local
|
| |
- socket paths.
|
| |
+ socket paths.
|
| |
|
| |
_Requirement_: Installation must occur in the same locations as
|
| |
traditional RPM software delivery.
|
| |
@@ -237,14 +237,14 @@
|
| |
schedules. There are two main aspects to this problem:
|
| |
|
| |
* A major version of a popular piece of software is released just after
|
| |
- a Fedora release, so it doesn’t land in Fedora for six months.
|
| |
+ a Fedora release, so it doesn’t land in Fedora for six months.
|
| |
* Some software does frequent major revisions (Django, Node.js, etc.)
|
| |
- and swapping them out every six months for the latest one means that
|
| |
- dependent projects are constantly needing to adapt to the new breakage
|
| |
- or find alternative mechanisms for retaining the older, working version
|
| |
+ and swapping them out every six months for the latest one means that
|
| |
+ dependent projects are constantly needing to adapt to the new breakage
|
| |
+ or find alternative mechanisms for retaining the older, working version
|
| |
* Some software does not handle multiple-version upgrades (Nextcloud,
|
| |
- for example). Attempting to go from version 15 to verison 19 requires
|
| |
- first upgrading through 16, 17, and 18.
|
| |
+ for example). Attempting to go from version 15 to verison 19 requires
|
| |
+ first upgrading through 16, 17, and 18.
|
| |
|
| |
_Requirement_: It must be possible for new alternative versions of
|
| |
software to become available to the Fedora Package Collection between
|
| |
jibecfed
commented 3 years ago
in the internationalization system of our docs, the tool po4a we use to convert asciidoc files into pot displays three lines of warning for each missing indentation.
most of the time it is cosmetic issues in adoc (like here), but sometimes it's po4a bugs that I want to see
this PR has no impact on your rendering, it is fully cosmetic