packaging/guidelines
6
2
Fork 11
Code Issues 111 Pull requests 27 Projects Releases Packages Wiki Activity Actions

Fix self-contradictory web assets guidelines #1539

Merged
james merged 2 commits from gotmax23/packaging-guidelines:web-no-self-contradict into main 2026-06-11 16:16:43 +00:00
Conversation 2 Commits 2 Files changed 2 +2 -4
1 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit a67b8eff31 - Show all commits

Clarify self-contradictory pre-generated CSS guideline

Prev Next 
See #1496.
The current text of the Guidelines are confusing because in once
paragraph it says CSS must be re-generated and in another it says it
doesn't have to be. This clarifies the text so it is inline with
decision made in https://pagure.io/fesco/issue/3269.
Maxwell G 2026-05-17 23:36:20 -05:00
commit a67b8eff31
Signed by: gotmax23
GPG key ID: F79E4E25E8C661F8

6
guidelines/modules/ROOT/pages/Web_Assets.adoc
View file

@ -102,12 +102,10 @@ unless stated otherwise in this document.
Pure CSS frameworks can be included as-is.
CSS frameworks that use an alternative language that compiles to CSS,
such as https://lesscss.org/[LESS],
must compile to CSS as part of the build process.
Packages containing CSS should make the best effort to regenerate any precompiled/minimized CSS wherever possible,
SHOULD compile to CSS as part of the build process,
as this leads to more maintainable packages.
Where this would result in a significant hardship,
the bundled pregenerated CSS may be shipped with a specfile comment explaining the decision.
bundled pregenerated CSS may be shipped with a specfile comment explaining the decision.
This does not eliminate the requirement to validate licenses of bundled content.
== Flash