Search results

=== Packaging Committee Report === * FESCo approved the Packaging Committee's guidelines regarding: ...

...r 2005, or maybe worse. This change will update the version and revamp the packaging completely. ...come from entirely different sources.) There are many bugs related to the packaging which can be resolved. We can also take advantage of weak dependencies. ...

...f the npm (Node-packaged modules) package manager and developing packaging guidelines around it. ...pm] and its dependency chain and [[PackagingDrafts:Node.js|draft packaging guidelines]] are being composed. ...

SCL - Software Collections - are popular packaging format above rpm. Let's enable them for Fedora. More details on [https://ww My first draft [https://fedoraproject.org/wiki/User:Mmaslano/SCLinFedora ] is obsoleted by ...

...he plan here is to get Fedora onto the stable series, which will allow for packaging of HTCondor point releases within a Fedora release. ...point releases. This brings the packages in line with the Fedora Packaging Guidelines. ...

=== Fedora Packaging Committee Meeting 2009-03-03 === | style="color: #407a40" | tibbs, which guidelines were approved by FESCo? ...

...and maintaining .spec files. We would like to avoid writing those Module Guidelines for the F26 cycle and instead '''limit the number of trusted module maintai <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it nee ...

{{admon/important | Comments and Explanations | MOSTLY EMPTY DRAFT}} * Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> ...

=== Fedora Packaging Committee Meeting of {2007.03.13} === ...ollowing drafts have been accepted by FESCO and are to be written into the guidelines: ...

...will research and develop new or improved methods of developing, testing, packaging and deploying software for the Fedora community. * Provides a list of tasks and goals which fulfil the mission of packaging, testing and delivering the various existing and new software stacks in Fed ...

* Policies and guidelines: N/A (not a System Wide Change) <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it nee ...

Currently, the [[Packaging:Guidelines#PIE|Packaging Guidelines]] allow Help writing the new packaging guidelines. ...

Current situation ("correct" means "follows current packaging guidelines"): * Policies and guidelines: ...

'''Initial Draft:''' 2016-01-13<BR> ...elines| Package Naming Guidelines]] and [[Packaging:Guidelines| Packaging Guidelines]]. There are also some packages that cannot be included in Fedora, to check ...

--[[User:Dmalcolm|Dmalcolm]] 00:27, 12 March 2010 (UTC): I believe this draft, as written, is controversial. For what it's worth, I strongly disagree wi [[Category:Packaging guidelines drafts]] ...

...chedule. We still do not have that many user services, and restarting from packaging scriptlets will be possible and appropriate only for some of them. I think We have rpm packaging scriptlets to reexecute systemd and restart system services as part of the ...

* Policies and guidelines: ** Packaging Guidelines need to reflect that license files must be tagged with %license instead of ...

* Hands-free packaging * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> ...

Changes in packaging: ** Discussing changes in Python packaging guidelines with Fedora community and FPC ...

* Packaging Committee Report: ...gDrafts/PHP were approved with the caveat that the macros mentioned in the draft don't exist in FC5 or less (so they can only apply to FC6). ...