From Fedora Project Wiki
- === Fedora Packaging Committee Meeting of {2007-08-28} === ...ollowing drafts have been accepted by FESCO and are to be written into the guidelines: ...7 KB (978 words) - 03:22, 21 December 2008
- = Guidelines for creating filesystem subpackages = = Filesystem Subpackages Guidelines = ...2 KB (248 words) - 18:06, 5 August 2009
- Robin 'cheese' Lee is working on packaging Zope2 and a bunch of its dependencies. == Dependency Graph of Zope packages (draft)== ...2 KB (346 words) - 09:48, 20 September 2010
- ...font packages, but a generic packaging consideration that could deserve a packaging guideline. Do not care at all whether symlinks are absolute or relative. No changes to guidelines are needed, and the related warnings should be disabled in the Fedora rpmli ...3 KB (395 words) - 18:16, 27 February 2009
- {{draft}} [[Category:Packaging guidelines drafts]] ...491 bytes (67 words) - 16:27, 12 May 2016
- == Current Text from Packaging/Guidelines for the FileAndDirectoryOwnership subsection == == Draft Addition to above text == ...2 KB (396 words) - 21:30, 21 February 2009
- ...g guidelines for Fedora projects. It also approves exemptions the various guidelines where required, as well as exemptions to the package review process. The Fedora Packaging Committee currently meets every Thursday at 17:00 UTC (16:00 UTC during US ...6 KB (919 words) - 19:46, 2 May 2024
- ...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 == Draft review template == ...6 KB (981 words) - 22:59, 18 February 2010
- === Fedora Packaging Committee Meeting of 2007.04.10 === There were no votes last week, so nothing added to the guidelines this week. ...9 KB (1,332 words) - 03:20, 21 December 2008
- [[Packaging:Guidelines#Tags]] This draft is not ready, yet. It is currently be worked on by [[User:Till|Till Maas]. ...4 KB (608 words) - 08:54, 18 September 2016
- ...evisions since import from moinmoin but also do not appear in the existing guidelines. If dropped or rejected, they should be archived. If active they should be |[[PackagingDrafts/ExplicitRequires]]|| Explicit Requires packaging guideline modifications || added || In progress ...20 KB (2,423 words) - 18:54, 27 February 2009
- = BuildRoot Guidelines = '''Initial Draft:''' Thursday October 26, 2017<BR> ...2 KB (251 words) - 09:28, 26 October 2017
- {{Draft}} No formal guidelines exist. "Best practices" at [[SIGs/KDE#Best_Practices]] ...2 KB (273 words) - 00:59, 6 August 2009
- == Comments moved from the bottom of the original draft == - I think referencing the GCJ Guidelines, which say the package should build on GCJ, is sufficient, since building o ...6 KB (988 words) - 01:51, 21 May 2012
- = Upstream Versioning Recommendation (Draft) = While [[Packaging:NamingGuidelines#Package_Version|Packaging Guidelines]] describes these cases in great detail, here we outline an abstract of the ...4 KB (647 words) - 16:13, 14 January 2011
- * Discuss new guidelines * Current Packaging draft will be submitted to FPC for approval (will not wait for JNI resolution) ...953 bytes (118 words) - 15:56, 16 March 2011
- = Improved Ivy Packaging = This change aims at improving the way of packaging Java software, which uses Apache Ivy to manage build dependencies. ...3 KB (403 words) - 11:49, 25 October 2014
- == Notes (draft) == === For the Tooling and Guidelines and Beyond === ...2 KB (241 words) - 10:43, 30 June 2016
- {{draft}} ...logs should be immutable. This is common sense, but is not codified in the guidelines currently ...1 KB (203 words) - 06:18, 25 January 2010
- = Draft package naming guidelines for TeX and LaTeX add on packages = ...aintained for some time now, and Jindrich Novy is planning to move over to packaging TeXLive as a replacement - see [[Releases/FeatureTexLive]] for details on ...2 KB (318 words) - 18:47, 27 February 2009