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

...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

[ ] 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.

= 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

...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>

...reference. '''This is not a policy nor should the notes be interpreted as guidelines!''' ...chives/fedora-packaging/2006-December/msg00066.html, http://www.redhat.com/archives/fedora-maintainers/2007-February/msg00328.html

...grant plugin configuration file upon installation. As most of the RubyGems guidelines apply to them, this guide discusses only specifics in which Vagrant plugins == Naming Guidelines ==

Using 'fedora-usermgmt' is optional and not required by packaging guidelines. When you want it for your package, register a user in the [[PackageUserReg * [https://www.redhat.com/archives/fedora-extras-list/2006-March/msg00688.html How fedora-usermgmt works]

...valuate the best way to have extras use updates-testing repository and the guidelines must be uniform for both) ''[I think this is overkill. What specific examp https://www.redhat.com/archives/fedora-test-list/2006-March/msg00455.html

Using 'fedora-usermgmt' is optional and not required by packaging guidelines. When you want it for your package, register a user in the [[PackageUserReg * [https://www.redhat.com/archives/fedora-extras-list/2006-March/msg00688.html How fedora-usermgmt works]

...tions. As a result packaging fonts will often require more legal work than packaging your average FLOSS app. Before you continue, check our [[Legal_consideratio # Fonts released upstream in separate archives '''MUST''' be packaged in separate source packages (''src.rpm''), unless th

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

...g. Please refer to the [[Packaging:Python_Old|previous version]] of these guidelines for older releases.}} ...e '''must''' provide <code>python3-example</code>. However, as the naming guidelines mandate that the python3 subpackage be named <code>python3-example</code>,

=== Fedora Packaging Committee Meeting of {2007-11-20} === * There are components of the proposal which go beyond packaging policy and are not considered by FPC. This includes the CompsPolicy docume