From Fedora Project Wiki

View ( | ) (20 | 50 | 100 | 250 | 500)
  • ...tory). This has to be done in sync with JRuby related changes to packaging guidelines. === New Packaging Guidelines === ...
    8 KB (1,291 words) - 04:09, 9 November 2013
  • === Fedora Packaging Committee Meeting of {2007-05-22} === * Tweaks to static library packaging guidelines: http://fedoraproject.org/wiki/PackagingDrafts/StaticLibraryChanges ...
    19 KB (2,759 words) - 03:21, 21 December 2008
  • * New Packaging Guidelines for Ruby packages (gems and extension libraries) * Changes to the location of files to comply with FHS, multilib and packaging standards ...
    9 KB (1,410 words) - 04:13, 9 November 2013
  • ...r-side JavaScript runtimes like Node.js [[Packaging:Node.js|have their own guidelines]], and software like GNOME which embeds JavaScript for extensions have thei <!--shamelessly stolen from Toshio's draft--> ...
    9 KB (1,410 words) - 19:01, 21 October 2013
  • === Fedora Packaging Committee Meeting of {2007-06-19} === ...ollowing drafts have been accepted by FESCO and are to be written into the guidelines: ...
    15 KB (2,155 words) - 03:21, 21 December 2008
  • {{Draft}} [[Category:Packaging guidelines drafts]] ...
    2 KB (292 words) - 16:01, 26 November 2010
  • === Fedora Packaging Committee Meeting of {2007-06-05} === * OCaml guidelines: http://fedoraproject.org/wiki/PackagingDrafts/OCaml ...
    14 KB (1,980 words) - 03:21, 21 December 2008
  • = Adopt new Go Packaging Guidelines = The [[PackagingDrafts/Go| current Go packaging guidelines]] have been in a draft ...
    6 KB (940 words) - 17:25, 9 July 2019
  • == EPEL 7 in Python 3 Plan Draft == ...jor version update" as specified in EPEL update guidelines [2]. And as the guidelines say, this should be avoided if at all possible. ...
    8 KB (1,260 words) - 18:43, 27 February 2015
  • ...packages into Fedora. This requires the specs to meet the Fedora Packaging Guidelines, be submitted for Review Request, reviewed and accepted into Fedora. * Fedora Musicians' Guide: currently in draft stage, this new guide will be published with Fedora 14. Testing and proof- ...
    2 KB (251 words) - 21:31, 17 September 2016
  • {{draft}} [[Category:Packaging guidelines drafts]] ...
    2 KB (277 words) - 15:19, 29 June 2011
  • = Subrelease Packaging Guidelines for JPackage RPMS = '''Initial Draft:''' Tuesday Jan 16, 2007<BR> ...
    9 KB (1,492 words) - 19:17, 17 February 2010
  • === Fedora Packaging Committee Meeting of {2007-06-26} === ...ollowing drafts have been accepted by FESCO and are to be written into the guidelines: ...
    19 KB (2,793 words) - 03:22, 21 December 2008
  • == No broken dependencies should be a packaging guideline == After further discussion, FESCo asked that Toshio and Richard draft up a ...
    3 KB (402 words) - 08:05, 18 September 2016
  • === Fedora Packaging Committee Meeting of {2008-03-11} === * Further questions were posed and will be relayed to the draft submitter. ...
    22 KB (3,150 words) - 03:23, 21 December 2008
  • * Design additional guidelines on top of the Fedora Packaging guidelines that are specific to audio packages (as needed) ...ges when the are imported into the Fedora Package Collection. This way the packaging expertise and manpower of the Fedora Community can be combined with the vas ...
    5 KB (830 words) - 21:52, 14 December 2023
  • {{admon/warning|This is a draft document}} [[Category:Packaging guidelines drafts]] ...
    5 KB (785 words) - 10:53, 30 January 2014
  • === Fedora Packaging Committee Meeting of {2007-10-16} === No new guidelines this week. ...
    14 KB (2,003 words) - 03:23, 21 December 2008
  • {{draft|Approved}} == Changes from original draft == ...
    11 KB (1,734 words) - 14:47, 16 November 2010
  • ...reference. '''This is not a policy nor should the notes be interpreted as guidelines!''' ...e not, some are more useful than others. These are not part of the actual draft, at least yet. Approach with care. ...
    4 KB (697 words) - 16:34, 24 May 2008
View ( | ) (20 | 50 | 100 | 250 | 500)