Search results

= Packaging Java Web Applications = {{admon/tip|Java Guidelines|

|'''rpmdev-diff'''||Diff contents of two archives |'''rpmdev-extract'''||Extract various archives, "tar xvf" style

The packaging guidelines are not clear in explaining why %makeinstall * If a package contains libtool archives, it can cause broken *.la files to be installed.

...e items should be merged in from the full [[Packaging/Guidelines|Packaging Guidelines]] but given that many reviewers base their reviews on the former also out o [] MUST: The package must be named according to the Package Naming Guidelines.

From the official packageing guidelines 1. The package must be named according to the Package Naming Guidelines

{{admon/note | FPC | This proposal was reviewed and approved by FPC on [[Packaging:Minutes/20090106|2009-01-06]].}} ...ackagers wasting time as they find new “interesting” ways to interpret the guidelines.

{{DISPLAYTITLE:Fedora Packaging Guidelines for Python}} ...g guidelines for Fedora projects. It also approves exemptions the various guidelines where required, as well as exemptions to the package review process.

[ ] Package is named according to the Package Naming Guidelines. [ ] Package meets the Packaging Guidelines.

- The package is named according to the Package Naming Guidelines. - The package meets the Packaging Guidelines.

Guidelines. [ ] MUST: The package must meet the Packaging Guidelines.

...w Template. It is based on the [[Packaging:ReviewGuidelines|package review guidelines]] and updated frequently. - MUST: package is named according to the Package Naming Guidelines

* MUST: The package must be named according to the Package Naming Guidelines . ...format %{name}.spec unless your package has an exemption on Package Naming Guidelines .

= Package Review Guidelines = ...on the [https://lists.fedoraproject.org/mailman/listinfo/packaging Fedora packaging list] .

Cloned from ["Packaging/ReviewGuidelines"] . = Package Review Guidelines =

...of the Haskell Special Interest Group is to maintain, grow, and guide the packaging of Haskell projects in Fedora. ...s://lists.fedoraproject.org/archives/list/haskell@lists.fedoraproject.org/ archives]) for general discussion

= Subrelease Packaging Guidelines for JPackage RPMS = ...rence purposes. The current JPackage Exception Policy can be found here: [[Packaging/JPackagePolicy]]}}

...kaging Guidelines, section [https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_using_forges_hosted_revision_control Referencing Source]}} This proposal is a requisite for the [[More_Go_packaging|More Go packaging draft]].

My template for review. This is only formated, slightly modified form of [[Packaging:ReviewGuidelines]] [] MUST: The package must be named according to the Package Naming Guidelines.<br>

...s|Packaging Guidelines]] and [[Packaging:NamingGuidelines|Packaging Naming Guidelines]] to see if it meets the requirements ** Read some other package submissions to learn about packaging and gain familiarity with the process and requirements. One way of doing th

[ ] Package is named according to the Package Naming Guidelines. [1] ...res, except for any that are listed in the exceptions section of Packaging Guidelines. [2]